[
https://issues.apache.org/jira/browse/FLINK-9682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16534747#comment-16534747
]
ASF GitHub Bot commented on FLINK-9682:
---------------------------------------
Github user yanghua commented on the issue:
https://github.com/apache/flink/pull/6266
@zentol yes, if the description is very long, that would be not suitable to
display, maybe other choose :
* show a tip with mouseover event?
* pop a window to display?
what about split this issue into two task?
* provide a `setDescription` API
* display it on the web page
> Add setDescription to execution environment and display it in the UI
> --------------------------------------------------------------------
>
> 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)
