[
https://issues.apache.org/jira/browse/BEAM-4283?focusedWorklogId=108159&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-108159
]
ASF GitHub Bot logged work on BEAM-4283:
----------------------------------------
Author: ASF GitHub Bot
Created on: 01/Jun/18 18:30
Start Date: 01/Jun/18 18:30
Worklog Time Spent: 10m
Work Description: chamikaramj commented on a change in pull request
#5464: [BEAM-4283] Write Nexmark execution times to bigquery
URL: https://github.com/apache/beam/pull/5464#discussion_r192479918
##########
File path:
sdks/java/nexmark/src/main/java/org/apache/beam/sdk/nexmark/Main.java
##########
@@ -146,13 +164,77 @@ private void appendPerf(
private static final String LINE =
"==========================================================================================";
- /**
- * Print summary of {@code actual} vs (if non-null) {@code baseline}.
- */
+ /** Send {@code nexmarkPerf} to BigQuery. */
+ @VisibleForTesting
+ static void writeQueryPerftoBigQuery(
Review comment:
Using any runner (for the second pipeline) is fine. But can you clarify why
you cannot use DirectRunner here ? Using DirectRunner will be the easiest
option if you want to push a small amount of data to BigQuery. You'll have to
create a new PipelineOptions object for this.
----------------------------------------------------------------
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:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 108159)
Time Spent: 2h 40m (was: 2.5h)
> Export nexmark execution times to bigQuery
> ------------------------------------------
>
> Key: BEAM-4283
> URL: https://issues.apache.org/jira/browse/BEAM-4283
> Project: Beam
> Issue Type: Sub-task
> Components: examples-nexmark
> Reporter: Etienne Chauchot
> Assignee: Etienne Chauchot
> Priority: Major
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> Nexmark only outputs the results collection to bigQuery and prints in the
> console the execution times. To supervise Nexmark execution times, we need to
> store them as well per runner/query/mode
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
