beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pawel Szczur (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (BEAM-315) GroupByKey/CoGroupByKey doesn't group correctly with FlinkPipelineRunner
Date Tue, 31 May 2016 14:51:13 GMT

    [ https://issues.apache.org/jira/browse/BEAM-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15307833#comment-15307833
] 

Pawel Szczur edited comment on BEAM-315 at 5/31/16 2:51 PM:
------------------------------------------------------------

Using bleeding-edge of Beam. I've noticed the problem around last Tuesday, so it's there at
least that long.

The bug appears with different key types. I've tried: Protocol Message, Tuple, Avro and simple
types.


was (Author: pawelszczur@gmail.com):
Using bleeding-edge of Beam. I've noticed the problem around last Thursday, so it's there
at least that long.

The bug appears with different key types. I've tried: Protocol Message, Tuple, Avro and simple
types.

> GroupByKey/CoGroupByKey doesn't group correctly with FlinkPipelineRunner
> ------------------------------------------------------------------------
>
>                 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
>         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)

Mime
View raw message