We are trying to submit Oozie sqoop jobs using the Oozie Web Services API, sqoop job proxy submission as documented here: https://oozie.apache.org/docs/4.1.0/WebServicesAPI.html#Proxy_Sqoop_Job_Submission We are working with a kerberized cluster with Knox gateway, and have not been able to find good documentation on how to implement the AuthOozieClient in an environment like this. (If anyone has some documentation they could share on this, that would be great!) The sqoop command is generated dynamically based on selections made by the user in a web interface, and the XML sent to Oozie. The jobs are going to the “default” queue, and we want them to go to their own queue. I have tried adding the following to the XML that is passed to the web service, but the jobs are still being submitted to the default queue: <property> <name>mapreduce.job.queuename</name> <value>sqoop</value> </property> Using this property when running sqoop from the command line, or adding it to a workflow.xml file in the configuration section, allows the jobs to be submitted to the sqoop queue. Does anyone know if this web service supports specifying properties other than the required and optional properties documented? Is there a different way to accomplish this while still using the sqoop job proxy submission? Thank you for any help you can provide. ... View more