falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ying Zheng (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FALCON-1111) Instance update on titan DB based on JMS notifications on workflow jobs
Date Thu, 18 Feb 2016 21:55:18 GMT

     [ 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 (see FALCON-1334).  (was: 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-)

> 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 (see
FALCON-1334).



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

Mime
View raw message