Support Questions
Find answers, ask questions, and share your expertise

Executing a saved Sqoop job does not use specified yarn queue

Rising Star

I have encountered an issue where sqoop does not recognize the queue when executing as a saved job. Running the following code executes, but is executed using the default queue

sqoop job -Dmapreduce.job.queuename=etl --exec job_name

It appears it may be the same issue as reported here:

Is there a known workaround?