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

Oozie Coordinator does not allow us to override hadoop credential provider factory at run time

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 4.2.0, 4.3.0
    • None
    • coordinator
    • None

    Description

      It looks like we cannot override hadoop.security.credential.provider.path defined in oozie-site.xml at run time per application basis without making changes to oozie-site.xml and restarting oozie service?
       
       I am interested in defining my coordinator like this where I need to monitor for availability of file in the S3 bucket which is controlled by access key and secret access key. This access key and secret access key is maintained in application specific JCEK file and hence I cannot define hadoop.security.credential.provider.path in core-site.xml or oozie-site.xml and I will need to pass this property dynamically for each coordinator. I believe this flexibility is not there. It will be good to add this feature
       
      <datasets>
      <dataset name="ix" frequency="${coord:days(1)}" initial-instance="2015-05-10T15:25Z" timezone="Europe/Zurich">
      <uri-template>s3a://mybucket/a/b/${YEAR}/${MONTH}/${DAY}/Success.txt</uri-template>
      </dataset>
      </datasets>

      Attachments

        Activity

          People

            Unassigned Unassigned
            krishmah Mahadevan Krishnan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: