You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Ying Zheng (JIRA)" <ji...@apache.org> on 2016/01/27 04:33:39 UTC

[jira] [Issue Comment Deleted] (FALCON-1776) Obtain lineage information, cluster, feed instance path for WAITING and TIMEOUT instances

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

Ying Zheng updated FALCON-1776:
-------------------------------
    Comment: was deleted

(was: Thank you for your suggestion, [~ajayyadava]. Instance dependency API you suggested looks more efficient than oozie to get lineage information, which is inferable from entity definition in Falcon.)

> 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)