[
https://issues.apache.org/jira/browse/BEAM-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391523#comment-16391523
]
Ahmet Altay commented on BEAM-3808:
-----------------------------------
As a note: the solution needs to be applied to dataflow runners in all
languages. Python currently truncates default job names to 63 characters by
truncating the user name where necessary and preserving date as much as
possible. We can converge on a strategy to keep most useful pieces in places.
> Dataflow Jobs meet Cloud Label Spec
> -----------------------------------
>
> Key: BEAM-3808
> URL: https://issues.apache.org/jira/browse/BEAM-3808
> Project: Beam
> Issue Type: Improvement
> Components: runner-dataflow
> Reporter: Andrea Foegler
> Assignee: Thomas Groh
> Priority: Major
>
> Dataflow Job Names should meet Cloud Label Specifications:
> [https://cloud.google.com/resource-manager/docs/creating-managing-labels]
> This will allow Dataflow users to organize resources according to the
> Dataflow Job using those resources. The Dataflow Service will be able to
> automatically associate accessed and consumed resources and associated
> metrics to support streamlined monitoring and analysis of these resources, in
> particular GCE instance usage metrics.
> Potential Issues: Some current users appear to encode a lot of data in their
> job names. Need to identify if applying this restriction breaks any
> necessary use cases and verify an alternative is available before proceeding.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
