[
https://issues.apache.org/jira/browse/BEAM-11267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17549055#comment-17549055
]
Danny McCormick commented on BEAM-11267:
----------------------------------------
This issue has been migrated to https://github.com/apache/beam/issues/20663
> 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
> Priority: P3
> 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.20.7#820007)
