Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Tue, 31 Mar 2015 01:06:53 +0000 (UTC)
From: "Zhijie Shen (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12784945.1427136557000.75158.1427764012996@Atlassian.JIRA>
In-Reply-To: <JIRA.12784945.1427136557000@Atlassian.JIRA>
References: <JIRA.12784945.1427136557000@Atlassian.JIRA>
 <JIRA.12784945.1427136557128@arcas>
Subject: [jira] [Updated] (YARN-3391) Clearly define flow ID/ flow run /
 flow version in API and storage
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Zhijie Shen updated YARN-3391:
------------------------------
    Attachment: YARN-3391.1.patch

Create a patch to fix the flow context info. I've updated the distributed shell accordingly. It worked end-to-end on my local box.

> 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
>         Attachments: YARN-3391.1.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)