From issues-return-176934-apmail-flink-issues-archive=flink.apache.org@flink.apache.org Thu Jul 12 09:48:02 2018 Return-Path: X-Original-To: apmail-flink-issues-archive@minotaur.apache.org Delivered-To: apmail-flink-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E7F0C181BF for ; Thu, 12 Jul 2018 09:48:02 +0000 (UTC) Received: (qmail 78365 invoked by uid 500); 12 Jul 2018 09:48:02 -0000 Delivered-To: apmail-flink-issues-archive@flink.apache.org Received: (qmail 78325 invoked by uid 500); 12 Jul 2018 09:48:02 -0000 Mailing-List: contact issues-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flink.apache.org Delivered-To: mailing list issues@flink.apache.org Received: (qmail 78316 invoked by uid 99); 12 Jul 2018 09:48:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Jul 2018 09:48:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 4D8671805D3 for ; Thu, 12 Jul 2018 09:48:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id Kye2Evh4uLsQ for ; Thu, 12 Jul 2018 09:48:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 2B1F15F1F0 for ; Thu, 12 Jul 2018 09:48:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 7B8D1E103D for ; Thu, 12 Jul 2018 09:48:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 2C8FC23F9A for ; Thu, 12 Jul 2018 09:48:00 +0000 (UTC) Date: Thu, 12 Jul 2018 09:48:00 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: issues@flink.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (FLINK-9682) Add setDescription to execution environment and display it in the UI MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/FLINK-9682?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1654= 1400#comment-16541400 ]=20 ASF GitHub Bot commented on FLINK-9682: --------------------------------------- Github user tillrohrmann commented on the issue: https://github.com/apache/flink/pull/6266 =20 I would be ok with splitting the work between the backend and frontend = work. =20 @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-3d2= 01bee-85c9-11e8-81e0-cf50afa86d0b.png) ![image](https://user-images.githubusercontent.com/5756858/42625914-45a= 7bdb2-85c9-11e8-88b5-460aa1e16c91.png) Where the red arrows are we could insert new columns for the descriptio= n. 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 envi= ronment. =C2=A0In an environment where many version of a job may be executi= ng, such as a development or test environment, identifying which running jo= b is of a specific version via the UI can be difficult unless the version i= s embedded into the job name given the {{execute}}. =C2=A0But the job name = is uses for other purposes, such as for namespacing metrics. =C2=A0Thus, it= is not ideal to modify the job name, as that could require modifying metri= c dashboards and monitors each time versions change. > I propose a new method be added to the execution environment, {{setDescri= ption}}, that would allow a user to pass in an arbitrary description that w= ould be displayed in the dashboard, allowing users to distinguish jobs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)