[
https://issues.apache.org/jira/browse/BEAM-11267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17270294#comment-17270294
]
Beam JIRA Bot commented on BEAM-11267:
--------------------------------------
This issue was marked "stale-assigned" and has not received a public comment in
7 days. It is now automatically unassigned. If you are still working on it, you
can assign it to yourself again. Please also give an update about the status of
the work.
> 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.3.4#803005)
