You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@oozie.apache.org by "abhishek bafna (JIRA)" <ji...@apache.org> on 2016/04/01 20:22:25 UTC

[jira] [Created] (OOZIE-2498) Oozie CallerId configuration for downstream components

abhishek bafna created OOZIE-2498:
-------------------------------------

             Summary: 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


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)