You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/08/09 17:07:01 UTC

[jira] [Commented] (BEAM-10228) Reshuffle seems to be dropping elements in streaming Dataflow pipeline.

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

Beam JIRA Bot commented on BEAM-10228:
--------------------------------------

This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.


> Reshuffle seems to be dropping elements in streaming Dataflow pipeline.
> -----------------------------------------------------------------------
>
>                 Key: BEAM-10228
>                 URL: https://issues.apache.org/jira/browse/BEAM-10228
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-dataflow, sdk-java-harness
>            Reporter: Daniel Oliveira
>            Priority: P2
>              Labels: stale-P2
>
> https://stackoverflow.com/questions/62017572/beam-java-dataflow-bigquery-streaming-insert-groupbykey-reducing-elements
> This showed up on SO and it shows a GBK in a reshuffle actually dropping elements. I asked the user if they've tried it on other runners, and from what I understood they tried with the Direct runner but never got to the point in the pipeline where the original issue occurred, so it's hard to tell if this is a runner or SDK issue. The user has also contacted Dataflow support.
> Not sure if this is high priority or not or who would be an appropriate assignee, so I'll just leave the bug unassigned for future reference, so if this pops up again there's evidence that it's been a problem. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)