[ 
https://issues.apache.org/jira/browse/BEAM-3046?focusedWorklogId=680642&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-680642
 ]

ASF GitHub Bot logged work on BEAM-3046:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 12/Nov/21 04:49
            Start Date: 12/Nov/21 04:49
    Worklog Time Spent: 10m 
      Work Description: AnandInguva commented on pull request #15919:
URL: https://github.com/apache/beam/pull/15919#issuecomment-966818655


   > Is this a proposal for what an API could look like?
   
   @robertwb Yes, it would be a new API for metrics. We need to write the 
metrics API in pythonic way


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 680642)
    Time Spent: 1h  (was: 50m)

> De-javafy the Python Metrics API
> --------------------------------
>
>                 Key: BEAM-3046
>                 URL: https://issues.apache.org/jira/browse/BEAM-3046
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-py-core
>            Reporter: Robert Bradshaw
>            Assignee: Ananda Prasad Inguva
>            Priority: P3
>              Labels: community-onboarding, starter, triaged
>             Fix For: 3.0.0
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> 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.20.1#820001)

Reply via email to