[
https://issues.apache.org/jira/browse/FALCON-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15254672#comment-15254672
]
Venkatesan Ramachandran commented on FALCON-1923:
-------------------------------------------------
The operation is derived from the workflow app name and populated in the text
message by the JMSMessageConsumer.createContext(). from the log message, it
looks like below with the operation attribute in there.
2016-04-22 20:32:40,463 INFO - [ActiveMQ Session Task-2:] ~ onWait
WorkflowExecutionContext{{nominalTime=2016-04-10-00-10, workflowUser=ambari-qa,
operation=IMPORT, parentId=0000125-160422014727119-oozie-oozi-C,
workflowEndTime=1461357160463, contextType=COORDINATOR_ACTION,
workflowId=0000125-160422014727119-oozie-oozi-C@2,
workflowStartTime=1461357160463, status=WAITING,
entityName=feed-import-filesystem, entityType=FEED}}
(MetadataMappingService:307)
> Add EntityOperations property in Oozie coordinators
> ---------------------------------------------------
>
> Key: FALCON-1923
> URL: https://issues.apache.org/jira/browse/FALCON-1923
> Project: Falcon
> Issue Type: Sub-task
> Reporter: Ying Zheng
> Assignee: Venkatesan Ramachandran
>
> Oozie JMS notifications on coordinator actions provide updates on waiting and
> timeout instances. These messages doesn't contain information on entity
> operation, which is needed when adding instances to Titan DB. Should include
> this property when generating Oozie coordinators.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
