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

Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2021/01/15 17:13:06 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17266206#comment-17266206 ] 

Beam JIRA Bot commented on BEAM-11267:
--------------------------------------

This issue is assigned but has not received an update in 30 days so it has been labeled "stale-assigned". If you are still working on the issue, please give an update and remove the label. If you are no longer working on the issue, please unassign so someone else may work on it. In 7 days the issue will be automatically unassigned.

> 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: P3
>              Labels: stale-assigned
>          Time Spent: 3h
>  Remaining Estimate: 0h
>
> 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)