beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rafael Fernandez (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (BEAM-2710) Outputing "finished" when processing is not called in ParDoTest.TestDoFn leads to unexpected ElementCount
Date Tue, 01 Aug 2017 23:22:00 GMT

     [ 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)

Mime
View raw message