hequn8128 opened a new pull request #11470: [FLINK-16671][python] Support for 
defining scopes and variables on Python metric group
URL: https://github.com/apache/flink/pull/11470
 
 
   
   ## What is the purpose of the change
   
   This pull request supports for defining scopes and variables on Python 
metric group, i.e., adding `get_metric_group()` on `FunctionContext`, adding 
`add_group`, `get_scope_components`, `get_all_variables` and 
`get_metric_identifier` in `MetricGroup`.
   
   
   ## Brief change log
   
     - Adds `get_metric_group()` on `FunctionContext`
     - Adds `add_group`, `get_scope_components`, `get_all_variables` and 
`get_metric_identifier` in `MetricGroup`
     - Adds `python.udf.metric.enabled` configuration to enable or disable 
metric for Python UDFs.
   
   
   ## Verifying this change
   
   This change added tests and can be verified as follows:
   
     - Adds tests in `testUDFProtoConstructedProperlyForSingleUDF` to verify 
the metric group proto info.
     - Adds test_metric to verify operations in Python MetricGroup.
     - Adds test_metric_it_case to verify metric group info which is passed 
from Java to Python
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (no)
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: (no)
     - The serializers: (no)
     - The runtime per-record code paths (performance sensitive): (no)
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (no)
     - The S3 file system connector: (no)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (yes)
     - If yes, how is the feature documented? (PythonDocs, Note: more 
documentation will be added in 
[FLINK-16674](https://issues.apache.org/jira/browse/FLINK-16674))
   

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


With regards,
Apache Git Services

Reply via email to