>
>
>
> *From:* ewenstep...@gmail.com [mailto:ewenstep...@gmail.com] *On Behalf
> Of *Stephan Ewen
> *Sent:* Monday, March 07, 2016 8:29 PM
> *To:* user@flink.apache.org
> *Subject:* Re: realtion between operator and task
>
>
>
> Hi!
>
>
>
> A "task&qu
operator and task
Hi!
A "task" is something that is deployed as one unit to the TaskManager and runs
in one thread.
A task can have multiple "operators" chained together, usually one per user
function, for example "Map -> Filter -> FlatMap -> AssignTimestamps -> .
Hi!
A "task" is something that is deployed as one unit to the TaskManager and
runs in one thread.
A task can have multiple "operators" chained together, usually one per user
function, for example "Map -> Filter -> FlatMap -> AssignTimestamps -> ..."
Stephan
On Mon, Mar 7, 2016 at 7:36 PM, Radu
Hi,
Can someone explain how and where a stream operator is mapped to a stream task.
I am particularly interested in the way the stream outputs are created and
attached to the operators. I saw that this happen in OperatorChain functions
but I do not have the picture of the lifecycle of an stream