[
https://issues.apache.org/jira/browse/BEAM-4374?focusedWorklogId=209915&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-209915
]
ASF GitHub Bot logged work on BEAM-4374:
----------------------------------------
Author: ASF GitHub Bot
Created on: 08/Mar/19 01:29
Start Date: 08/Mar/19 01:29
Worklog Time Spent: 10m
Work Description: ajamato commented on issue #7982: [BEAM-4374] Add
MetricResultMatcher verification for user counters, GCK element count, and
process time to wordcount_it_test
URL: https://github.com/apache/beam/pull/7982#issuecomment-470768675
Just realized that the test is not in a dataflow specific folder. It seems
to use the dataflow runner, but really should be moved I suppose. I am thinking
that I might just port this code to a new test case file under
sdks/python/runners/dataflow
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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: 209915)
Time Spent: 8h 50m (was: 8h 40m)
> Update existing metrics in the FN API to use new Metric Schema
> --------------------------------------------------------------
>
> Key: BEAM-4374
> URL: https://issues.apache.org/jira/browse/BEAM-4374
> Project: Beam
> Issue Type: New Feature
> Components: beam-model
> Reporter: Alex Amato
> Priority: Major
> Time Spent: 8h 50m
> Remaining Estimate: 0h
>
> Update existing metrics to use the new proto and cataloging schema defined in:
> [_https://s.apache.org/beam-fn-api-metrics_]
> * Check in new protos
> * Define catalog file for metrics
> * Port existing metrics to use this new format, based on catalog
> names+metadata
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
