You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/11/02 17:11:00 UTC

[jira] [Commented] (BEAM-7934) Dataflow Python SDK logging: step_id is always empty string

    [ https://issues.apache.org/jira/browse/BEAM-7934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17224817#comment-17224817 ] 

Beam JIRA Bot commented on BEAM-7934:
-------------------------------------

This issue was marked "stale-P2" and has not received a public comment in 14 days. It is now automatically moved to P3. If you are still affected by it, you can comment and move it back to P2.

> 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
>            Priority: P3
>
> 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)