You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Lukasz Gajowy (JIRA)" <ji...@apache.org> on 2019/01/10 15:22:00 UTC

[jira] [Work started] (BEAM-6290) Make the schema for BQ tables storing metric results more generic (JAVA)

     [ https://issues.apache.org/jira/browse/BEAM-6290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on BEAM-6290 started by Lukasz Gajowy.
-------------------------------------------
> Make the schema for BQ tables storing metric results more generic (JAVA)
> ------------------------------------------------------------------------
>
>                 Key: BEAM-6290
>                 URL: https://issues.apache.org/jira/browse/BEAM-6290
>             Project: Beam
>          Issue Type: Sub-task
>          Components: testing
>            Reporter: Lukasz Gajowy
>            Assignee: Lukasz Gajowy
>            Priority: Major
>          Time Spent: 10m
>  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)