[
https://issues.apache.org/jira/browse/FALCON-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15170405#comment-15170405
]
Ajay Yadava edited comment on FALCON-1776 at 2/27/16 7:04 AM:
--------------------------------------------------------------
It is documented in the documentation of InstanceDependency :)
[link|https://github.com/apache/falcon/blob/master/docs/src/site/twiki/falconcli/DependencyInstance.twiki]
You can't use Oozie query for most of the cases. For example a feed instance
available now may be consumed by a process instance which will run in future
and this information can not be pulled from Oozie. I suspect you don't require
both side of dependencies and only a part of existing lineage (where it ran,
path etc.) and it will be easier for you to just pull that information from
oozie / fetching it on jms notifications etc. to populate the titan DB.
was (Author: ajayyadava):
It is documented in the documentation of InstanceDependency :)
[link](https://github.com/apache/falcon/blob/master/docs/src/site/twiki/falconcli/DependencyInstance.twiki)
You can't use Oozie query for most of the cases. For example a feed instance
available now may be consumed by a process instance which will run in future
and this information can not be pulled from Oozie. I suspect you don't require
both side of dependencies and only a part of existing lineage (where it ran,
path etc.) and it will be easier for you to just pull that information from
oozie / fetching it on jms notifications etc. to populate the titan DB.
> Instance update on titan DB based on JMS notifications on coordinator actions
> -----------------------------------------------------------------------------
>
> 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 information
> on lineage, cluster, and feed instance path (see example below). Need to
> obtain these information for WAITING and TIMEOUT instances before adding them
> to titan DB.
> 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)
