[jira] [Updated] (FALCON-1111) Instance update on titan DB based on JMS notifications on workflow jobs

["Balu Vellanki (JIRA)" <ji...@apache.org>]

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

Balu Vellanki updated FALCON-1111:
----------------------------------
    Fix Version/s:     (was: trunk)
                   0.10

> 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
>             Fix For: 0.10
>
>
> Today, Falcon adds instances to titan DB if and only if WF succeeds. To use titan DB for instance search and lineage queries, instances of different statuses need to be added. This jira is to add running, succeeded, failed, killed 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). Waiting and timeout instances will be added in FALCON-1776 based on JMS notifications on coordinator jobs.



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