a question about CopyingChainOutput

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

a question about CopyingChainOutput

Ma GuoWei

hi,all 

The class CopyingChainOutput always setKeyContextElement1 but the second operator of "chain" is not keyedstream any more.

I think this is no use to setKeyContextElement1.

do i miss something?

thanks for any help.






Reply | Threaded
Open this post in threaded view
|

Re: a question about CopyingChainOutput

Aljoscha Krettek-2
Hi,
you are right. Only the first operator in a chain can be a keyed operator. Therefore, the “setKeyContextElement1” call is currently unnecessary. If you want you can open an issue for that and work on removing it.

Cheers,
Aljoscha

> On 16 Mar 2016, at 09:24, Ma GuoWei <[hidden email]> wrote:
>
> hi,all
> The class CopyingChainOutput always setKeyContextElement1 but the second operator of "chain" is not keyedstream any more.
> I think this is no use to setKeyContextElement1.
> do i miss something?
> thanks for any help.
>
>
>
>
>

Reply | Threaded
Open this post in threaded view
|

答复: a question about CopyingChainOutput

Ma GuoWei
i am glad to do that!

i will do that after my work!

thanks!

________________________________________
发件人: Aljoscha Krettek <[hidden email]>
发送时间: 2016年3月16日 9:07
收件人: [hidden email]
主题: Re: a question about CopyingChainOutput

Hi,
you are right. Only the first operator in a chain can be a keyed operator. Therefore, the “setKeyContextElement1” call is currently unnecessary. If you want you can open an issue for that and work on removing it.

Cheers,
Aljoscha

> On 16 Mar 2016, at 09:24, Ma GuoWei <[hidden email]> wrote:
>
> hi,all
> The class CopyingChainOutput always setKeyContextElement1 but the second operator of "chain" is not keyedstream any more.
> I think this is no use to setKeyContextElement1.
> do i miss something?
> thanks for any help.
>
>
>
>
>