[
https://issues.apache.org/jira/browse/TEZ-900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14306043#comment-14306043
]
Hitesh Shah commented on TEZ-900:
---------------------------------
Looking at the code, I think the fix belongs in
TezYarnClient::submitApplication(). After the submit calls come back, you can
introduce a call to getApplicationReport and throw an exception if the app is
in a failed state. This approach will result in a common fix that applies to
both session and non-session modes.
As for the unit test, you can test this by adding a test to TestTezJobs with an
invalid queue name set in the conf used to initialize a tezclient and then
testing both session and non-session mode failures.
> Confusing message for incorrect queue for some tez examples
> -----------------------------------------------------------
>
> Key: TEZ-900
> URL: https://issues.apache.org/jira/browse/TEZ-900
> Project: Apache Tez
> Issue Type: Bug
> Affects Versions: 0.3.0
> Reporter: Jonathan Eagles
> Assignee: Chang Li
> Attachments: tez900.patch, tez900_v2.patch, tez900_v3.patch
>
>
> The error message of at least orderedwordcount with non-existent queue is
> very difficult as compared to mrrsleep which is very intuitive.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
