You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@beam.apache.org by "Rafael Fernandez (JIRA)" <ji...@apache.org> on 2017/08/01 23:22:00 UTC

[jira] [Closed] (BEAM-2710) Outputing "finished" when processing is not called in ParDoTest.TestDoFn leads to unexpected ElementCount

     [ https://issues.apache.org/jira/browse/BEAM-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rafael Fernandez closed BEAM-2710.
----------------------------------
       Resolution: Not A Problem
    Fix Version/s: Not applicable

The issue is broader than test -- it's in worker code.

> Outputing "finished" when processing is not called in ParDoTest.TestDoFn leads to unexpected ElementCount
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: BEAM-2710
>                 URL: https://issues.apache.org/jira/browse/BEAM-2710
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-core
>            Reporter: Rafael Fernandez
>            Assignee: Davor Bonaci
>            Priority: Trivial
>             Fix For: Not applicable
>
>
> While it is legal to call finishBundle even if processElement was not called (say, when processing an empty input PCollection), it's best to guard against this case if we're examining correctness of outputs. Specifically, I was surprised at seeing ElementCount = 1 instead of 0 -- essentially, "finished" was being counted here.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)