Hi Robert,
the number of parallel subtasks is the parallelism of the job or the
individual operator. Only when executing Flink locally, the parallelism is
set to the CPU cores.
The number of groups generated by the groupBy() transformation doesn't
affect the parallelism. Very often the number of g
Within the mapper you cannot access the parallelism of the following nor
preceding operation.
On 20.06.2016 15:56, Paschek, Robert wrote:
Hi Mailing list,
using a RichMapPartitionFunction i can access the total number m of this mapper
utilized in my job with
int m = getRuntimeContext().getNum