Uploaded image for project: 'Falcon'
  1. Falcon
  2. FALCON-1333 Support instance search of a group of entities
  3. FALCON-1111

Instance update on titan DB based on JMS notifications on workflow jobs

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 0.10
    • common, messaging

    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.

      Attachments

        Issue Links

          is required by

          Sub-task - The sub-task of the issue FALCON-1334 Improve search performance with Titan graph database indexing

          • Major - Major loss of function.
          • Resolved

          Sub-task - The sub-task of the issue FALCON-1335 Backend support of instance search of a group of entities

          • Major - Major loss of function.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. FALCON-1776 Process instance update in titan DB based on JMS notifications on coordinator actions

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              ying-eng Ying Zheng
              sowmyaramesh Sowmya Ramesh
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Slack

                  Issue deployment