[OOZIE-2498] Oozie CallerId configuration for downstream components

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.3.0
• Component/s: core
• Labels: patch
• Assignee: Abhishek Bafna
• Reporter: Abhishek Bafna
• Created: 01/Apr/16 18:21
• Updated: 02/Dec/16 21:04
• Resolved: 19/Sep/16 17:21

Description

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).

Issue Links

• links to: Review Board Link