You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2020/11/16 14:55:00 UTC

[jira] [Updated] (BEAM-11267) Remove unnecessary reshuffle for stateful ParDo after keyed operation

     [ https://issues.apache.org/jira/browse/BEAM-11267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kenneth Knowles updated BEAM-11267:
-----------------------------------
    Status: Open  (was: Triage Needed)

> Remove unnecessary reshuffle for stateful ParDo after keyed operation
> ---------------------------------------------------------------------
>
>                 Key: BEAM-11267
>                 URL: https://issues.apache.org/jira/browse/BEAM-11267
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-flink
>            Reporter: David Morávek
>            Assignee: David Morávek
>            Priority: P0
>
> When we have stateful pardo after GBK / Combine, we can safely assume that partitioning remains consistent and we can safe an extra shuffle.
> The use case for this are user defined timers / datadriven triggers. This code path is stressed for example by org.apache.beam.sdk.transforms.ParDoTest.TimerTests#testGbkFollowedByUserTimers.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)