beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jingsong Lee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-2140) Fix SplittableDoFn ValidatesRunner tests in FlinkRunner
Date Tue, 09 May 2017 16:43:04 GMT

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

Jingsong Lee commented on BEAM-2140:
------------------------------------

1. {{SplittableParDo}} will clear its State, in {{SplittableParDo.ProcessFn.processElement()}}
{code}
    if (result.getResidualRestriction() == null) {
        // All work for this element/restriction is completed. Clear state and release hold.
        elementState.clear();
        restrictionState.clear();
        holdState.clear();
        return;
      }
{code}

I got values up to 12344 in intellij debug mode while got values up to 34567 in intellij run
mode.(No matter what outputWatermark of {{BoundedSourceWrapper}}) 
So I think the processing of SDF has nothing to do with inputWatermark, and ProcessTimeService
only related. 

This question should be caused by the second and third points.

> Fix SplittableDoFn ValidatesRunner tests in FlinkRunner
> -------------------------------------------------------
>
>                 Key: BEAM-2140
>                 URL: https://issues.apache.org/jira/browse/BEAM-2140
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-flink
>            Reporter: Aljoscha Krettek
>            Assignee: Aljoscha Krettek
>
> As discovered as part of BEAM-1763, there is a failing SDF test. We disabled the tests
to unblock the open PR for BEAM-1763.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message