[ https://issues.apache.org/jira/browse/BEAM-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15311980#comment-15311980
]
Pawel Szczur edited comment on BEAM-315 at 6/2/16 8:54 AM:
-----------------------------------------------------------
As far as I understand the issue there are 3 places it may originate from:
1. windowing (all items should end up in one global pane)
2. shuffle (is windowing considered during shuffle?)
3. sorting items in a given shard (is windowing considered?)
Am I correct?
was (Author: pawelszczur@gmail.com):
As far as I understand the issue there are 3 places it may originate from:
1. windowing (all items should end up in one global pane)
2. shuffle (is windowing considered during shuffle?)
3. sorting items in a given shard (is sorting considered?)
Am I correct?
> Flink Runner compares keys unencoded which may produce incorrect results
> ------------------------------------------------------------------------
>
> Key: BEAM-315
> URL: https://issues.apache.org/jira/browse/BEAM-315
> Project: Beam
> Issue Type: Bug
> Components: runner-flink
> Affects Versions: 0.1.0-incubating
> Reporter: Pawel Szczur
> Assignee: Aljoscha Krettek
> Attachments: CoGroupPipelineStringKey.java
>
>
> Same keys are processed multiple times.
> A repo to reproduce the bug:
> https://github.com/orian/cogroup-wrong-grouping
> Discussion:
> http://mail-archives.apache.org/mod_mbox/incubator-beam-user/201605.mbox/%3CCAB2uKkG2xHsWpLFUkYnt8eEzdxU%3DB_nu6crTwVi-ZuUpugxkPQ%40mail.gmail.com%3E
> Notice: I haven't tested other runners (didn't manage to configure Spark).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
|