beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BEAM-2732) State tracking in Python is inefficient and has duplicated code
Date Thu, 11 Jan 2018 19:33:00 GMT


ASF GitHub Bot commented on BEAM-2732:

pabloem opened a new pull request #4395: [BEAM-2732] Logging relies on statesampler state
   This PR depends on PR #4375, and PR #4387.
   This PR is a backward-compatible change that allows logging to rely on statesampler state
to provide the current step name.
   This change should enable all clients to stop using the legacy logging to switch state
across every operation, and start using statesampler for that.
   This change should not have a significant performance impact, as JsonLogFormatter was already
relying on a Thread local to retrieve the logging information.

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:

> State tracking in Python is inefficient and has duplicated code
> ---------------------------------------------------------------
>                 Key: BEAM-2732
>                 URL:
>             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

View raw message