[
https://issues.apache.org/jira/browse/YARN-4445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059190#comment-15059190
]
Hadoop QA commented on YARN-4445:
---------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 5s {color}
| {color:red} YARN-4445 does not apply to trunk. Rebase required? Wrong Branch?
See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12777861/YARN-4445.patch |
| JIRA Issue | YARN-4445 |
| Powered by | Apache Yetus 0.1.0 http://yetus.apache.org |
| Console output |
https://builds.apache.org/job/PreCommit-YARN-Build/9996/console |
This message was automatically generated.
> 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)
