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/10/19 17:10:01 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=17216931#comment-17216931 ]
Beam JIRA Bot commented on BEAM-7934:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.
> 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: P2
> Labels: stale-P2
>
> 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)