[
https://issues.apache.org/jira/browse/BEAM-11267?focusedWorklogId=512603&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-512603
]
ASF GitHub Bot logged work on BEAM-11267:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 16/Nov/20 21:23
Start Date: 16/Nov/20 21:23
Worklog Time Spent: 10m
Work Description: je-ik commented on pull request #13353:
URL: https://github.com/apache/beam/pull/13353#issuecomment-728337299
Do we have a test (in flink runner) for the GBK -> stateful pardo pair? Not
sure if there is one in ValidatesRunner suite.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 512603)
Time Spent: 1h 10m (was: 1h)
> 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
> Time Spent: 1h 10m
> 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)
