[
https://issues.apache.org/jira/browse/AMBARI-10997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14534277#comment-14534277
]
Oleg Nechiporenko commented on AMBARI-10997:
--------------------------------------------
+1 for patch
> 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)
