[
https://issues.apache.org/jira/browse/BEAM-3046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17145359#comment-17145359
]
Beam JIRA Bot commented on BEAM-3046:
-------------------------------------
This issue was marked "stale-P2" and has not received a public comment in 14
days. It is now automatically moved to P3. If you are still affected by it, you
can comment and move it back to P2.
> 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
> Priority: P3
> Labels: community-onboarding, 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)
