[
https://issues.apache.org/jira/browse/BEAM-2732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319265#comment-16319265
]
ASF GitHub Bot commented on BEAM-2732:
--------------------------------------
pabloem opened a new pull request #4375: [BEAM-2732] Starting refactor of state
tracking in Python
URL: https://github.com/apache/beam/pull/4375
The goal for BEAM-2732 is to refactor the context trackers in the Python SDK
so that they will all use the same mechanism.
Currently, Metrics, Logging and StateSampler keep their own contexts.
BEAM-2732 aims to have all of them rely on the logic in StateSampler to keep
their context (this is already the case in Java).
This PR does the following:
* Clean up legacy code in the StateSampler.
* Adds a global per-thread variable for state sampler, so each execution
thread will be able to access the current state sampler from this global
variable (this will then be used for LoggingContext, and
MetricsEnvironment.current_container).
* Gives the Python-only state sampler functionality to track context, so
that non-Cythonized runners can rely on the StateSampler to track context.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> State tracking in Python is inefficient and has duplicated code
> ---------------------------------------------------------------
>
> Key: BEAM-2732
> URL: https://issues.apache.org/jira/browse/BEAM-2732
> Project: Beam
> Issue Type: Bug
> Components: sdk-py-core
> Reporter: Pablo Estrada
> Assignee: Pablo Estrada
>
> e.g logging and metrics keep state separately. State tracking should be
> unified.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
