[
https://issues.apache.org/jira/browse/BEAM-11030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17212210#comment-17212210
]
Ismaël Mejía commented on BEAM-11030:
-------------------------------------
I see, good to know it is unrelated. Any eventual candidate to take a look at
this? It is a minor issue but I am afraid it is might be hiding something else.
> 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)
