We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The Yarn CommandLine always commits tasks to the default queue, even if the tenant YARN queue is specified.
Task should be committed to the tenant YARN queue.
Run a non-sql Flink job >=1.12 with specific tenant YARN queue.
No response
3.1.x
The text was updated successfully, but these errors were encountered:
Thank you for your feedback, we have received your issue, Please wait patiently for a reply.
#troubleshooting
Sorry, something went wrong.
More: I found the way to determine YARN queue in sql mode was also wrong, I will fix it in the same pr.
ORuteMa
Successfully merging a pull request may close this issue.
Search before asking
What happened
The Yarn CommandLine always commits tasks to the default queue, even if the tenant YARN queue is specified.
What you expected to happen
Task should be committed to the tenant YARN queue.
How to reproduce
Run a non-sql Flink job >=1.12 with specific tenant YARN queue.
Anything else
No response
Version
3.1.x
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: