You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/04/01 21:53:00 UTC

[jira] [Work logged] (BEAM-12083) Nexmark Query 13

     [ https://issues.apache.org/jira/browse/BEAM-12083?focusedWorklogId=575770&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-575770 ]

ASF GitHub Bot logged work on BEAM-12083:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 01/Apr/21 21:52
            Start Date: 01/Apr/21 21:52
    Worklog Time Spent: 10m 
      Work Description: amaliujia commented on pull request #14404:
URL: https://github.com/apache/beam/pull/14404#issuecomment-812191393


   R: @y1chi 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 575770)
    Time Spent: 20m  (was: 10m)

> 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
>          Time Spent: 20m
>  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)