Re: Events B33/35 in Parallel Streams Diagram

Sure, that would be great! Thanks! 2016-09-29 17:43 GMT+02:00 Neil Derraugh < neil.derra...@intellifylearning.com>: > Hi Fabian, > > Yes. Thanks! I think it would be helpful to indicate that on the graph. > Call it “key” or “key_id" instead of just “id”, as it is in fact the key of > the stream

Re: Events B33/35 in Parallel Streams Diagram

Hi Fabian, Yes. Thanks! I think it would be helpful to indicate that on the graph. Call it “key” or “key_id" instead of just “id”, as it is in fact the key of the stream and not the id of the event? Probably seems trivial, but I struggled with this one. haha. I’ll submit a PR for the docs

Re: Events B33/35 in Parallel Streams Diagram

Hi Neil, "B" only refers to the key-part of the record, the number is the timestamp (as you assumed out). The payload of the record is not displayed in the figure. So B35 and B31 are two different records with identical key. The keyBy() operation sends all records with the same key to the same sub

Events B33/35 in Parallel Streams Diagram

Hi, I’m confused about the meaning of event(s?) B33 and B35 in the Parallel Streams Diagram (https://ci.apache.org/projects/flink/flink-docs-master/dev/event_time.html#watermarks-in-parallel-streams