[
https://issues.apache.org/jira/browse/BEAM-3046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17439721#comment-17439721
]
Beam JIRA Bot commented on BEAM-3046:
-------------------------------------
This issue is assigned but has not received an update in 30 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> De-javafy the Python Metrics API
> --------------------------------
>
> Key: BEAM-3046
> URL: https://issues.apache.org/jira/browse/BEAM-3046
> Project: Beam
> Issue Type: Bug
> Components: sdk-py-core
> Reporter: Robert Bradshaw
> Assignee: Ananda Prasad Inguva
> Priority: P3
> Labels: community-onboarding, stale-assigned, starter, triaged
> Fix For: 3.0.0
>
>
> For example, though Java forces one to put all stand-alone functions as
> static methods on a class (like Metrics) in Python one would just have
> standard module-level functions.
> Also, the MetricsFilter builder pattern is very Java-esque (and verbose). In
> Python, one would simply let result.metrics() take keyword arguments.
> We should seriously consider aggregating rather than returning lists of
> results, at least by default. E.g. in
> https://github.com/apache/beam/blob/master/sdks/python/apache_beam/examples/wordcount.py
> it assumes that there's no other metric with the given name in any
> subtransform (otherwise it may deterministically grab the "wrong" one.)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
