hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Varun Saxena (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-4445) Unify the term flowId and flowName in timeline v2 codebase
Date Sat, 21 Oct 2017 06:06:56 GMT

     [ 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

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message