You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Rui Wang (Jira)" <ji...@apache.org> on 2021/04/01 19:48:00 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 ]

Rui Wang updated BEAM-12083:
----------------------------
    Summary: Nexmark Query 13  (was: Nexmark Query 14)

> 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
>
> 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 14, 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)