You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Ismaël Mejía (Jira)" <ji...@apache.org> on 2021/03/30 13:17:00 UTC
[jira] [Updated] (BEAM-11030) Nexmark Query 3 produces inconsistent
output size on Direct runner
[ https://issues.apache.org/jira/browse/BEAM-11030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ismaël Mejía updated BEAM-11030:
--------------------------------
Priority: P2 (was: P3)
> 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)