[
https://issues.apache.org/jira/browse/FALCON-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15116495#comment-15116495
]
Ying Zheng commented on FALCON-1776:
------------------------------------
[~ajayyadava] This is for instance search and lineage API with Titan DB. We
update Titan DB based on the JMS notification. For WAITING and TIMEOUT
instances, the notification comes from the coordinator action where the lineage
information, cluster and feed instance path are not provided in the JMS
message. We need cluster information to create instance node, feed instance
path to create feed instance node; and lineage information for lineage API.
> Obtain lineage information, cluster, feed instance path for WAITING and
> TIMEOUT instances
> -----------------------------------------------------------------------------------------
>
> Key: FALCON-1776
> URL: https://issues.apache.org/jira/browse/FALCON-1776
> Project: Falcon
> Issue Type: Sub-task
> Reporter: Ying Zheng
>
> In the JMS notifications from the coordinator action, there is no lineage
> information (see example below). Need to obtain lineage information before
> adding the instances. The existing Triage function provides input feeds but
> no output feeds. Plan to extend this function to obtain output information as
> well.
> 2016-01-21 19:33:58,934 INFO - [ActiveMQ Session Task:] ~ onWait
> WorkflowExecutionContext{{workflowId=0000002-160120223952090-oozie-oozi-C@1,
> workflowUser=ambari-qa, nominalTime=2015-05-01-00-00,
> entityName=pig-process-0515, workflowEndTime=1453404838892, status=WAITING,
> workflowStartTime=1453404838892, contextType=COORDINATOR_ACTION,
> entityType=PROCESS}} (MetadataMappingService:311)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
