Mailing-List: contact dev-help@falcon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@falcon.apache.org
Date: Thu, 18 Feb 2016 21:54:18 +0000 (UTC)
From: "Ying Zheng (JIRA)" <jira@apache.org>
To: dev@falcon.incubator.apache.org
Message-ID: <JIRA.12783092.1426728618000.87350.1455832458147@Atlassian.JIRA>
In-Reply-To: <JIRA.12783092.1426728618000@Atlassian.JIRA>
References: <JIRA.12783092.1426728618000@Atlassian.JIRA>
 <JIRA.12783092.1426728618859@arcas>
Subject: [jira] [Updated] (FALCON-1111) Instance update on titan DB based on
 JMS notifications on workflow jobs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ying Zheng updated FALCON-1111:
-------------------------------
    Description: Today, Falcon adds instances to titan DB if and only if WF succeeds. To use titan DB for instance search and also to extend lineage feature for running/failed instances, instances of different status need to be added to titan DB. Created this jira to add running, succeeded, failed, and suspended instances to titan DB based on JMS notifications on workflow jobs. Instance-entity edge properties (e.g. nominal time, status) are also added for vertex-centric indexing in FALCON-  (was: Today, Falcon only adds instances to graph DB if WF succeeds. To use graph DB for search functionality and also to extend lineage feature for running/failed instances, instances will be added in the "Pre Processing" action and updated accordingly when the WF succeeds/fails in "Post Processing" action. Also need to update the status for rerun and error scenarios.)

> Instance update on titan DB based on JMS notifications on workflow jobs
> -----------------------------------------------------------------------
>
>                 Key: FALCON-1111
>                 URL: https://issues.apache.org/jira/browse/FALCON-1111
>             Project: Falcon
>          Issue Type: Sub-task
>          Components: common, messaging
>            Reporter: Sowmya Ramesh
>            Assignee: Ying Zheng
>              Labels: Lineage
>
> Today, Falcon adds instances to titan DB if and only if WF succeeds. To use titan DB for instance search and also to extend lineage feature for running/failed instances, instances of different status need to be added to titan DB. Created this jira to add running, succeeded, failed, and suspended instances to titan DB based on JMS notifications on workflow jobs. Instance-entity edge properties (e.g. nominal time, status) are also added for vertex-centric indexing in FALCON-


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