You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Varun Saxena (JIRA)" <ji...@apache.org> on 2017/10/21 06:06:56 UTC
[jira] [Updated] (YARN-4445) Unify the term flowId and flowName in
timeline v2 codebase
[ https://issues.apache.org/jira/browse/YARN-4445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Varun Saxena updated YARN-4445:
-------------------------------
Fix Version/s: 2.9.0
> 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
> Fix For: 2.9.0, 3.0.0-alpha1
>
> Attachments: YARN-4445-feature-YARN-2928.001.patch, 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.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org