Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 2A80E200D16 for ; Mon, 25 Sep 2017 13:43:05 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 294671609C4; Mon, 25 Sep 2017 11:43:05 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 7C0D31609E9 for ; Mon, 25 Sep 2017 13:43:04 +0200 (CEST) Received: (qmail 91988 invoked by uid 500); 25 Sep 2017 11:43:03 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 91896 invoked by uid 99); 25 Sep 2017 11:43:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Sep 2017 11:43:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id D35C2C2E60 for ; Mon, 25 Sep 2017 11:43:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id KpXwyHE8veYs for ; Mon, 25 Sep 2017 11:43:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id EC1BB610D0 for ; Mon, 25 Sep 2017 11:43: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 5E86AE0F0B for ; Mon, 25 Sep 2017 11:43:01 +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 A764B2423A for ; Mon, 25 Sep 2017 11:43:00 +0000 (UTC) Date: Mon, 25 Sep 2017 11:43:00 +0000 (UTC) From: "Akhil PB (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-6652) Merge flow info and flow runs MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 25 Sep 2017 11:43:05 -0000 [ https://issues.apache.org/jira/browse/YARN-6652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178883#comment-16178883 ] Akhil PB commented on YARN-6652: -------------------------------- Assigning ticket to myself. > Merge flow info and flow runs > ----------------------------- > > Key: YARN-6652 > URL: https://issues.apache.org/jira/browse/YARN-6652 > Project: Hadoop YARN > Issue Type: Sub-task > Components: yarn-ui-v2 > Affects Versions: 3.0.0-alpha2 > Reporter: Haibo Chen > Assignee: Akhil PB > > If a user clicks on a flow from the flow activity page, Flow Run and Flow Info are shown separately. Usually, users want to go to individual flow runs. With the current work flow, the user will need to click on Flow Run because Flow Info is selected by default. > Given that Flow Info does not have much information, It'd be a nice improvement if we can show flow info and flow run together, that is, one section at the top containing flow info, another section at the bottom containing the flow runs -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org