[
https://issues.apache.org/jira/browse/BEAM-12083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17380064#comment-17380064
]
Beam JIRA Bot commented on BEAM-12083:
--------------------------------------
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 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)
