Mailing-List: contact dev-help@falcon.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@falcon.incubator.apache.org
Date: Fri, 28 Feb 2014 19:40:24 +0000 (UTC)
From: "Venkatesh Seetharam (JIRA)" <jira@apache.org>
To: dev@falcon.incubator.apache.org
Message-ID: <JIRA.12692597.1391204063281.126684.1393616424189@arcas>
In-Reply-To: <JIRA.12692597.1391204063281@arcas>
References: <JIRA.12692597.1391204063281@arcas>
Subject: [jira] [Commented] (FALCON-286) Capture information in process
 entity about the user workflow
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/FALCON-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13916246#comment-13916246 ] 

Venkatesh Seetharam commented on FALCON-286:
--------------------------------------------

bq.  so the coord-id itself can act as a distinct identifier for a version. 
is Falcon version bad? I can use coord-id as well but this is in the workflow.

bq. We ought to have a better way of setting falcon-workflow version for replication/retention.
What would that be? 

> Capture information in process entity about the user workflow
> -------------------------------------------------------------
>
>                 Key: FALCON-286
>                 URL: https://issues.apache.org/jira/browse/FALCON-286
>             Project: Falcon
>          Issue Type: Sub-task
>    Affects Versions: 0.5
>            Reporter: Venkatesh Seetharam
>            Assignee: Venkatesh Seetharam
>              Labels: lineage
>         Attachments: FALCON-286.patch
>
>


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)