[
https://issues.apache.org/jira/browse/BEAM-5906?focusedWorklogId=163564&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-163564
]
ASF GitHub Bot logged work on BEAM-5906:
----------------------------------------
Author: ASF GitHub Bot
Created on: 07/Nov/18 18:21
Start Date: 07/Nov/18 18:21
Worklog Time Spent: 10m
Work Description: lgajowy commented on issue #6886: [BEAM-5906] Use
dedicated BigQuery client for publishing Nexmark results
URL: https://github.com/apache/beam/pull/6886#issuecomment-436726025
Thanks! I rebased and applied your suggestions (except one). I will check if
rows aren't overwritten (as Etienne suggested) and test it with the new
dependency version tomorrow, so please don't merge this yet.
----------------------------------------------------------------
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: 163564)
Time Spent: 3h (was: 2h 50m)
> Remove pipeline for publishing nexmark results to bigQuery and publish using
> BigQuery API only
> ----------------------------------------------------------------------------------------------
>
> Key: BEAM-5906
> URL: https://issues.apache.org/jira/browse/BEAM-5906
> Project: Beam
> Issue Type: Improvement
> Components: examples-nexmark
> Reporter: Lukasz Gajowy
> Assignee: Lukasz Gajowy
> Priority: Minor
> Time Spent: 3h
> Remaining Estimate: 0h
>
> There's no need to start a separate pipeline for uploading metrics results
> from Nexmark suites to BigQuery. We can use an API designed for that and
> place it in test-utils. Thanks to that:
> - it won't start a separate pipeline every time it publishes results
> - other suites will be able to use that code
> - We will not face problems like special long to int conversion due to
> problems in BigQueryIO (eg. BEAM-4734) because we will use a thin API instead.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
