[
https://issues.apache.org/jira/browse/BEAM-11267?focusedWorklogId=512567&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-512567
]
ASF GitHub Bot logged work on BEAM-11267:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 16/Nov/20 20:16
Start Date: 16/Nov/20 20:16
Worklog Time Spent: 10m
Work Description: dmvk commented on a change in pull request #13353:
URL: https://github.com/apache/beam/pull/13353#discussion_r524545316
##########
File path:
runners/flink/src/main/java/org/apache/beam/runners/flink/translation/wrappers/streaming/WorkItemKeySelector.java
##########
@@ -49,6 +52,6 @@ public ByteBuffer
getKey(WindowedValue<SingletonKeyedWorkItem<K, V>> value) thro
@Override
public TypeInformation<ByteBuffer> getProducedType() {
- return new GenericTypeInfo<>(ByteBuffer.class);
+ return new CoderTypeInformation<>(FlinkKeyUtils.ByteBufferCoder.of(),
pipelineOptions.get());
Review comment:
Not sure if this is necessary. I wanted to ensure that the new
"reinterpreted partitioning" is compatible with the one used by GBK / Combine.
The idea was if partitioning is not compatible, it may result in some state
partitioning related glitches (eg. you wouldn't have local state for a
key-group you need).
Second thoughts, flink selects target partition based on "pojo hash code"
(not based on binary representation), so the previous version was probably
compatible enough 🤔
@mxm WDYT?
----------------------------------------------------------------
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: 512567)
Time Spent: 0.5h (was: 20m)
> 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: 0.5h
> 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)
