beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pei He (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (BEAM-545) Pipelines and their executions naming changes
Date Tue, 04 Oct 2016 20:21:20 GMT

     [ https://issues.apache.org/jira/browse/BEAM-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Pei He updated BEAM-545:
------------------------
    Component/s: sdk-java-core

> Pipelines and their executions naming changes
> ---------------------------------------------
>
>                 Key: BEAM-545
>                 URL: https://issues.apache.org/jira/browse/BEAM-545
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-core
>            Reporter: Pei He
>            Assignee: Pei He
>            Priority: Minor
>
> The purpose of the changes is to clarify the differences between the two, have
> consensus between runners, and unify the implementation.
> Current states:
>  * PipelineOptions.appName defaults to mainClass name
>  * DataflowPipelineOptions.jobName defaults to appName+user+datetime
>  * FlinkPipelineOptions.jobName defaults to appName+user+datetime
> Proposal:
> 1. Replace PipelineOptions.appName with PipelineOptions.pipelineName.
>     *  It is the user-visible name for a specific graph.
>     *  default to mainClass name.
>     *  Use cases: Find all executions of a pipeline
> 2. Add jobName to top level PipelineOptions.
>     *  It is the unique name for an execution
>     *  defaults to pipelineName + user + datetime + random Integer
>     *  Use cases:
>         -- Finding all executions by USER_A between TIME_X and TIME_Y
>         -- Naming resources created by the execution. for example:



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message