flink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gyula Fóra <gyf...@apache.org>
Subject Re: [DISCUSS] Behaviour of startNewChain() in Streaming
Date Mon, 25 May 2015 08:37:57 GMT
I see your point but this is a general problem with any property that we
set on the operators itself. Same goes for instance for parallelism :

input
  .map(new Map1())
  .setParallelism(2)
  .map(new Map2))
  .print()

Do we change the parallelism after map 1 so it applies to map 2?

Gyula


On Mon, May 25, 2015 at 10:26 AM, Aljoscha Krettek <aljoscha@apache.org>
wrote:

> Hi,
> I think people will be confused by the behaviour of startNewChain() in
> the streaming API. I myself had wrong assumptions about how it behaves
> when I was writing a test Job and the only other Job where someone not
> coming from Streaming wrote a Streaming Test is also making wrong
> assumptions. (StreamCheckpointingITCase, I'm not saying that's a
> stupid mistake, I made the same mistake myself.)
>
> So what chains of operators should this snipped produce:
>
> input
>   .map(new Map1())
>   .map(new Map2())
>   .startNewChain()
>   .map(new Map3())
>   .print()
>
> I would guess that your assumption about where the split in the chains
> happens here is wrong. :D
>
> Cheers,
> Aljoscha
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message