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

ASF GitHub Bot commented on FLINK-9682:
---------------------------------------

dawidwys commented on a change in pull request #6266: [FLINK-9682] Add 
setDescription to execution environment and provide description field for the 
rest api
URL: https://github.com/apache/flink/pull/6266#discussion_r216248829
 
 

 ##########
 File path: 
flink-core/src/main/java/org/apache/flink/api/common/ExecutionConfig.java
 ##########
 @@ -103,6 +103,8 @@
         */
        private int maxParallelism = -1;
 
+       private String description;
 
 Review comment:
   If you implemented it the same way as jobName, you would have it there in 
the `OptimizedPlan`

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Add setDescription to execution environment and provide description field for 
> the rest api
> ------------------------------------------------------------------------------------------
>
>                 Key: FLINK-9682
>                 URL: https://issues.apache.org/jira/browse/FLINK-9682
>             Project: Flink
>          Issue Type: Improvement
>          Components: DataStream API, Webfrontend
>    Affects Versions: 1.5.0
>            Reporter: Elias Levy
>            Assignee: vinoyang
>            Priority: Major
>              Labels: pull-request-available
>
> Currently you can provide a job name to {{execute}} in the execution 
> environment.  In an environment where many version of a job may be executing, 
> such as a development or test environment, identifying which running job is 
> of a specific version via the UI can be difficult unless the version is 
> embedded into the job name given the {{execute}}.  But the job name is uses 
> for other purposes, such as for namespacing metrics.  Thus, it is not ideal 
> to modify the job name, as that could require modifying metric dashboards and 
> monitors each time versions change.
> I propose a new method be added to the execution environment, 
> {{setDescription}}, that would allow a user to pass in an arbitrary 
> description that would be displayed in the dashboard, allowing users to 
> distinguish jobs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to