hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Li Lu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4445) Unify the term flowId and flowName in timeline v2 codebase
Date Thu, 17 Dec 2015 00:27:46 GMT

    [ https://issues.apache.org/jira/browse/YARN-4445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15061212#comment-15061212

Li Lu commented on YARN-4445:

All failing system tests passed on my local machine. +1. Since it has been hanging here for
about a day, I'm committing this shortly. 

> 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-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

This message was sent by Atlassian JIRA

View raw message