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

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

                Author: ASF GitHub Bot
            Created on: 21/Nov/18 16:28
            Start Date: 21/Nov/18 16:28
    Worklog Time Spent: 10m 
      Work Description: lgajowy commented on issue #7090:  [BEAM-5984] Enable 
publishing load test results to Big Query
URL: https://github.com/apache/beam/pull/7090#issuecomment-440728089
 
 
   @pabloem I refactored a little bit more so that more code could be reused 
(please see the new [commit 
description](https://github.com/apache/beam/pull/7090/commits/5617d5f4215e4eeabf8b187e12724c20c4528e7c))
   
   What is more, current implementation allows us to easily make code 
responsible for publishing to console common too. I didn't want to do this now 
because the change would be huge. 
   
   Could you take a look again?

----------------------------------------------------------------
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: 168345)
    Time Spent: 1h 20m  (was: 1h 10m)

> Publish metrics from load tests to BigQuery database
> ----------------------------------------------------
>
>                 Key: BEAM-5984
>                 URL: https://issues.apache.org/jira/browse/BEAM-5984
>             Project: Beam
>          Issue Type: Sub-task
>          Components: testing
>            Reporter: Lukasz Gajowy
>            Assignee: Lukasz Gajowy
>            Priority: Major
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Collect metrics in BQ so that those could be read and plotted using 
> PerfKitExplorer tool or any other similar. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to