[ https://issues.apache.org/jira/browse/OOZIE-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
abhishek bafna updated OOZIE-2498: ---------------------------------- Fix Version/s: 4.3.0 > Oozie CallerId configuration for downstream components > ------------------------------------------------------- > > Key: OOZIE-2498 > URL: https://issues.apache.org/jira/browse/OOZIE-2498 > Project: Oozie > Issue Type: Improvement > Components: core > Reporter: abhishek bafna > Assignee: abhishek bafna > Labels: patch > Fix For: 4.3.0 > > 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)