[
https://issues.apache.org/jira/browse/AMBARI-10997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14534656#comment-14534656
]
Hadoop QA commented on AMBARI-10997:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12731428/AMBARI-10997.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 24 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
contrib/views/hive.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/2661//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/2661//console
This message is automatically generated.
> Improve Error Handling - hive view
> ----------------------------------
>
> Key: AMBARI-10997
> URL: https://issues.apache.org/jira/browse/AMBARI-10997
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-views
> Affects Versions: 2.1.0
> Reporter: Erik Bergenholtz
> Assignee: Antonenko Alexander
> Fix For: 2.1.0
>
> Attachments: AMBARI-10997.patch
>
>
> We should handle the most common cases better than how we do it today. For
> example
> * Syntax Error
> * Non Existent Table Selected
> * Non Existent Column Selected
> * Bad Query
> In the above cases we get a certain exception back from Hive and should be
> able to show a more meaningful message back to the user (as well as the
> underlying exception). We should continue to allow the stack trace to be
> shown, but this should not be the default behavior.
> In the cases where we don't "understand" the cause of the error, we should
> continue to use the existing behavior.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
