flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-9682) Add setDescription to execution environment and display it in the UI
Date Thu, 12 Jul 2018 09:48:00 GMT

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

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

Github user tillrohrmann commented on the issue:

    https://github.com/apache/flink/pull/6266
  
    I would be ok with splitting the work between the backend and frontend work.
    
    @zentol  raised an important point which is where to place the content. Wha about the
following proposal?
    ![image](https://user-images.githubusercontent.com/5756858/42625904-3d201bee-85c9-11e8-81e0-cf50afa86d0b.png)
    ![image](https://user-images.githubusercontent.com/5756858/42625914-45a7bdb2-85c9-11e8-88b5-460aa1e16c91.png)
    Where the red arrows are we could insert new columns for the description. But I'm not
a terribly good web designer...



> 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)

Mime
View raw message