falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ying Zheng (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FALCON-1776) Process Instance update on titan DB based on JMS notifications on coordinator actions
Date Fri, 12 Aug 2016 20:29:20 GMT

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

Ying Zheng updated FALCON-1776:
-------------------------------
    Summary: Process Instance update on titan DB based on JMS notifications on coordinator
actions  (was: Instance update on titan DB based on JMS notifications on coordinator actions)

> Process 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: Improvement
>            Reporter: Ying Zheng
>            Assignee: Ying Zheng
>             Fix For: trunk
>
>
> 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)

Mime
View raw message