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 Sat, 07 Jul 2018 12:57:00 GMT

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

ASF GitHub Bot commented on FLINK-9682:

Github user yanghua commented on the issue:

    @hequn8128 thanks for your suggestion. Yes, cutting off the description is a choice. But
currently, for the web UI, if the description does not show in a new line, there is only little
zone can be used. In this situation, if we cut off the description would confuse users.

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

View raw message