[FALCON-1111] Instance update on titan DB based on JMS notifications on workflow jobs

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.10
• Component/s: common, messaging
• Labels: Lineage
• Assignee: Ying Zheng
• Reporter: Sowmya Ramesh
• Created: 19/Mar/15 01:30
• Updated: 06/Jun/16 21:32
• Resolved: 05/Mar/16 01:19

Description

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.

Issue Links

• is required by: FALCON-1334 Improve search performance with Titan graph database indexing
• is required by: FALCON-1335 Backend support of instance search of a group of entities
• is required by: FALCON-1776 Process instance update in titan DB based on JMS notifications on coordinator actions