Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-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 323DD18DBE for ; Tue, 15 Dec 2015 23:54:48 +0000 (UTC) Received: (qmail 51220 invoked by uid 500); 15 Dec 2015 23:54:47 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 51118 invoked by uid 500); 15 Dec 2015 23:54:47 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 50795 invoked by uid 99); 15 Dec 2015 23:54:46 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Dec 2015 23:54:46 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id CBF842C1F6B for ; Tue, 15 Dec 2015 23:54:46 +0000 (UTC) Date: Tue, 15 Dec 2015 23:54:46 +0000 (UTC) From: "Zhan Zhang (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (YARN-4445) Unify the term flowId and flowName in timeline v2 codebase MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-4445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhan Zhang updated YARN-4445: ----------------------------- Attachment: YARN-4445.patch > Unify the term flowId and flowName in timeline v2 codebase > ---------------------------------------------------------- > > Key: YARN-4445 > URL: https://issues.apache.org/jira/browse/YARN-4445 > Project: Hadoop YARN > Issue Type: Sub-task > Components: timelineserver > Reporter: Li Lu > Assignee: Zhan Zhang > Labels: refactor > Attachments: YARN-4445.patch > > > Flow names are not sufficient to identify a flow. I noticed we used both "flowName" and "flowId" to point to the same thing. We need to unify them to flowName. Otherwise, front end users may think flow id is a top level concept and try to directly locate a flow by its flow id. -- This message was sent by Atlassian JIRA (v6.3.4#6332)