[
https://issues.apache.org/jira/browse/BEAM-12083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17340946#comment-17340946
]
Beam JIRA Bot commented on BEAM-12083:
--------------------------------------
This issue is assigned but has not received an update in 30 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> 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
> Assignee: Rui Wang
> Priority: P2
> Labels: stale-assigned
> 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)
