[
https://issues.apache.org/jira/browse/BEAM-6291?focusedWorklogId=189909&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-189909
]
ASF GitHub Bot logged work on BEAM-6291:
----------------------------------------
Author: ASF GitHub Bot
Created on: 25/Jan/19 09:25
Start Date: 25/Jan/19 09:25
Worklog Time Spent: 10m
Work Description: kkucharc commented on issue #7614: [BEAM-6291] Generic
BigQuery schema load tests metrics
URL: https://github.com/apache/beam/pull/7614#issuecomment-457509628
Hi @udim I know that you reviewed similar code for Java recently, so I hope
that you will find a few minutes to take a look at this PR as well. I based my
BQ changes on your code. Other two commits are small fixes.
@pabloem and @lgajowy I would be grateful if you will check this too.
----------------------------------------------------------------
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: 189909)
Time Spent: 20m (was: 10m)
> Make the schema for BQ tables storing metric results more generic (Python)
> --------------------------------------------------------------------------
>
> Key: BEAM-6291
> URL: https://issues.apache.org/jira/browse/BEAM-6291
> Project: Beam
> Issue Type: Sub-task
> Components: testing
> Reporter: Lukasz Gajowy
> Assignee: Kasia Kucharczyk
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, we keep the metrics results in BQ in tables with a schema like
> this:
> timestamp | total_bytes | run_time | (possibly other BQ columns)
> every time we want to add a new column the schema has to be extended. This is
> not convenient given the fact that any load test can have different metrics
> stored. This in turn would cause multiple BQ tables each queried differently.
> We can provide a more generic schema, like so:
> test_id | timestamp | metric | value
> thanks to that, every metric, whatever it's name is, can be saved in the
> table as a separate row. This gives more elasticity in storing metrics and is
> still easy to query and plot.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
