[ https://issues.apache.org/jira/browse/OOZIE-3180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16360741#comment-16360741 ]
Steve Loughran commented on OOZIE-3180: --------------------------------------- HADOOP-14507 might help here > Oozie Coordinator does not allow us to override hadoop credential provider > factory at run time > ---------------------------------------------------------------------------------------------- > > Key: OOZIE-3180 > URL: https://issues.apache.org/jira/browse/OOZIE-3180 > Project: Oozie > Issue Type: Improvement > Components: coordinator > Affects Versions: 4.2.0, 4.3.0 > Reporter: Mahadevan Krishnan > Priority: Major > > 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> -- This message was sent by Atlassian JIRA (v7.6.3#76005)