[jira] [Comment Edited] (BEAM-11030) Nexmark Query 3 produces inconsistent output size on Direct runner

["Luke Cwik (Jira)" <ji...@apache.org>]

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

Luke Cwik edited comment on BEAM-11030 at 10/7/20, 4:45 PM:
------------------------------------------------------------

The inconsistent output has been going on since before April 16th, several months before the SDF migration for DirectRunner started.


was (Author: lcwik):
The inconsistent output has been going on since before April 16th.

> Nexmark Query 3 produces inconsistent output size on Direct runner
> ------------------------------------------------------------------
>
>                 Key: BEAM-11030
>                 URL: https://issues.apache.org/jira/browse/BEAM-11030
>             Project: Beam
>          Issue Type: Test
>          Components: runner-direct, testing-nexmark
>            Reporter: Ismaël Mejía
>            Priority: P2
>
> It seems that Direct runner is producing inconsitent outputs for Nexmark Query 3. All other runners produce constant output and even the SQL based queries on Direct runner do, so worth investigating.
> This happens in both batch and streaming.
> [http://104.154.241.245/d/x51DT0OMk/nexmark-output-size?orgId=1&from=now-6M&to=now&var-processingType=batch&var-ID=3&var-runner=DirectRunner]
>  



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