[
https://issues.apache.org/jira/browse/BEAM-4376?focusedWorklogId=108714&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-108714
]
ASF GitHub Bot logged work on BEAM-4376:
----------------------------------------
Author: ASF GitHub Bot
Created on: 04/Jun/18 19:47
Start Date: 04/Jun/18 19:47
Worklog Time Spent: 10m
Work Description: iemejia commented on issue #5549: [BEAM-4376] Add
Nexmark events generation based on ParDo
URL: https://github.com/apache/beam/pull/5549#issuecomment-394476160
Hi thanks for your comments in the queries, they highlight some valid
issues. I just want to clarify one thing. Both executions were done against the
normal DirectRunner but one used a synthetic generator based on the `Source`
API and the other a new one based on `Create.of(Void)+ParDo`. So I don't expect
such a big variability. I validated and both are producing exactly the same
'Inputs' so that's where I am lost, I expected some queries to eventually vary
but this goes beyond all my expectatives, in particular for queries like query
11.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 108714)
Time Spent: 50m (was: 40m)
> Add Nexmark events generation based on ParDo
> --------------------------------------------
>
> Key: BEAM-4376
> URL: https://issues.apache.org/jira/browse/BEAM-4376
> Project: Beam
> Issue Type: Improvement
> Components: examples-nexmark
> Reporter: Ismaël Mejía
> Assignee: Ismaël Mejía
> Priority: Minor
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Currently Nexmark generates events using the Source API. Having a ParDo based
> generator will allow us to use Nexmark quickly with the Portable runners.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
