[
https://issues.apache.org/jira/browse/BEAM-7934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17121939#comment-17121939
]
Kenneth Knowles commented on BEAM-7934:
---------------------------------------
This issue is assigned but has not received an update in 30 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> Dataflow Python SDK logging: step_id is always empty string
> -----------------------------------------------------------
>
> Key: BEAM-7934
> URL: https://issues.apache.org/jira/browse/BEAM-7934
> Project: Beam
> Issue Type: Bug
> Components: runner-dataflow, sdk-py-core
> Affects Versions: 2.13.0
> Reporter: James Hutchison
> Assignee: Ahmet Altay
> Priority: P2
> Labels: stale-assigned
>
> Using the dataflow runner, log messages always show up in stackdriver with
> the step_id as the empty string, so filtering log messages for a step doesn't
> work.
> {code:java}
> resource: {
> labels: {
> job_id: "<job id>"
> job_name: "<job name>"
> project_id: "<project id>"
> region: "<region>"
> step_id: ""
> }
> type: "dataflow_step"
> }{code}
> Another user seems to have posted in the old github repo and appears to be
> seeing the same problem based on their output:
> [https://github.com/GoogleCloudPlatform/DataflowPythonSDK/issues/62]
> From what I can tell is only affecting streaming pipelines
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
