[
https://issues.apache.org/jira/browse/OOZIE-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15222112#comment-15222112
]
abhishek bafna commented on OOZIE-2498:
---------------------------------------
Currently added the CallerId configuration for Pig and Hive action. The
workflow id will is set as the CallerId with a "oozie:" prefix.
Please review the attached patch.
> Oozie CallerId configuration for downstream components
> -------------------------------------------------------
>
> Key: OOZIE-2498
> URL: https://issues.apache.org/jira/browse/OOZIE-2498
> Project: Oozie
> Issue Type: Bug
> Components: core
> Reporter: abhishek bafna
> Attachments: OOZIE-2498-01.patch
>
>
> The idea is to add callerId to every component, so we can track the chain of
> application which cause the underlining operation. A typical chain is
> Oozie->Pig|Hive->Tez->Hdfs. With proper callerId logging, we can trace Hdfs
> operation back to Oozie workflow which triggers it.
> For Oozie, It will pass its workflow id as callerId to other components
> (Pig/Hive).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
