[
https://issues.apache.org/jira/browse/FALCON-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ying Zheng updated FALCON-1776:
-------------------------------
Description: In the JMS notifications from the coordinator action, there is
no information on timestamp. Need to allow the timestamp property to be
optional when adding process instance to titan DB. (was: 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))
> 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 timestamp. Need to allow the timestamp property to be optional when adding
> process instance to titan DB.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
