[
https://issues.apache.org/jira/browse/BEAM-2732?focusedWorklogId=118551&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-118551
]
ASF GitHub Bot logged work on BEAM-2732:
----------------------------------------
Author: ASF GitHub Bot
Created on: 03/Jul/18 01:34
Start Date: 03/Jul/18 01:34
Worklog Time Spent: 10m
Work Description: charlesccychen commented on a change in pull request
#5356: [BEAM-2732][BEAM-4028] Logging relies on StateSampler for context
URL: https://github.com/apache/beam/pull/5356#discussion_r199661924
##########
File path: sdks/python/apache_beam/runners/worker/logger.py
##########
@@ -49,7 +48,7 @@ def get_data(self):
per_thread_worker_data = _PerThreadWorkerData()
-class PerThreadLoggingContext(LoggingContext):
+class PerThreadLoggingContext(object):
Review comment:
Are we able to get rid of this class entirely? It looks like you removed
the only usage in operations.py.
----------------------------------------------------------------
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]
Issue Time Tracking
-------------------
Worklog Id: (was: 118551)
Time Spent: 16.5h (was: 16h 20m)
> 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
> Priority: Major
> Time Spent: 16.5h
> Remaining Estimate: 0h
>
> e.g logging and metrics keep state separately. State tracking should be
> unified.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
