Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BA35517228 for ; Wed, 25 Mar 2015 22:43:04 +0000 (UTC) Received: (qmail 77447 invoked by uid 500); 25 Mar 2015 22:42:54 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 77416 invoked by uid 500); 25 Mar 2015 22:42:54 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 77327 invoked by uid 99); 25 Mar 2015 22:42:54 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Mar 2015 22:42:54 +0000 Date: Wed, 25 Mar 2015 22:42:54 +0000 (UTC) From: "Vrushali C (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14380939#comment-14380939 ] Vrushali C commented on YARN-3391: ---------------------------------- Suggestions: bq. Flow run id should be a number as opposed to a generic string? Yes, it may be a good idea to have the flow run id as a long (epoch timestamp in milliseconds). bq. Default behavior for the flow run id if it is missing (i.e. client did not set it) The default flow run id can be the submit time of the flow. > 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 > > 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)