You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2021/07/13 17:21:01 UTC
[jira] [Updated] (BEAM-12083) Nexmark Query 13
[ https://issues.apache.org/jira/browse/BEAM-12083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Beam JIRA Bot updated BEAM-12083:
---------------------------------
Labels: stale-P2 (was: )
> Nexmark Query 13
> ----------------
>
> Key: BEAM-12083
> URL: https://issues.apache.org/jira/browse/BEAM-12083
> Project: Beam
> Issue Type: New Feature
> Components: testing-nexmark
> Reporter: Rui Wang
> Priority: P2
> Labels: stale-P2
> Time Spent: 5h
> Remaining Estimate: 0h
>
> In portability world, we expect on workers there are runners and SDKs. Current Nexmark queries, e.g. Nexmark Query 0, does not stress the boundary between runner and SDK.
> So I propose to have Nexmark query 13, which contains a source + GBK + ParDo, to stress the boundary between runner and SDK.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)