[
https://issues.apache.org/jira/browse/BEAM-11030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17248032#comment-17248032
]
Beam JIRA Bot commented on BEAM-11030:
--------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> 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
> Labels: stale-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)
