Uploaded image for project: 'Oozie'
  1. Oozie
  2. OOZIE-1871

Investigate if we can propagate the delegation token to the action conf from the Oozie server instead of action



    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • trunk
    • None
    • security
    • None


      Currently, Oozie prepares a configuration for the action to use when launching MR jobs. Oozie also provides an environment variable with the location of the tokens file. It is up to the action's Main to:

      1. Load the Configuration
      2. Get the location of the Token file
      3. Propagate the token file to the loaded Configuration
      4. Pass the Configuration to the CLI/MR Job/etc

      This isn't too much of a problem for most actions because we handle this for the user, but for the Java action, it's 4 not-obvious steps. We should investigate if we can make this one step by having the Configuration prepared by the Oozie server already have the token file propagated to it; then actions would have 2 steps:

      1. Load the Configuration
      2. Pass the Configuration to the CLI/MR Job/etc
        And the tokens would be handled automatically.

      We'd still have to provide the environment variable for backwards compatibility and flexibility reasons though.




            rkanter Robert Kanter
            rkanter Robert Kanter
            0 Vote for this issue
            2 Start watching this issue