[jira] [Resolved] (YARN-3391) Clearly define flow ID/ flow run / flow version in API and storage

["Junping Du (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/YARN-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Junping Du resolved YARN-3391.
------------------------------
          Resolution: Fixed
       Fix Version/s: YARN-2928
    Target Version/s: YARN-2928
        Hadoop Flags: Reviewed

I have commit this patch to branch YARN-2928. Thanks [~zjshen] for the patch contribution! Also, thank u, [~sjlee0], [~vrushalic] and [~jrottinghuis] for review and comments!

> Clearly define flow ID/ flow run / flow version in API and storage
> ------------------------------------------------------------------
>
>                 Key: YARN-3391
>                 URL: https://issues.apache.org/jira/browse/YARN-3391
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Zhijie Shen
>            Assignee: Zhijie Shen
>             Fix For: YARN-2928
>
>         Attachments: YARN-3391.1.patch, YARN-3391.2.patch, YARN-3391.3.patch, YARN-3391.4.patch, YARN-3391.5.patch
>
>
> To continue the discussion in YARN-3040, let's figure out the best way to describe the flow.
> Some key issues that we need to conclude on:
> - How do we include the flow version in the context so that it gets passed into the collector and to the storage eventually?
> - Flow run id should be a number as opposed to a generic string?
> - Default behavior for the flow run id if it is missing (i.e. client did not set it)
> - How do we handle flow attributes in case of nested levels of flows?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)