Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Thu, 7 May 2015 13:59:00 +0000 (UTC)
From: "Erik Bergenholtz (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12828017.1431007095000.36174.1431007140522@Atlassian.JIRA>
In-Reply-To: <JIRA.12828017.1431007095000@Atlassian.JIRA>
References: <JIRA.12828017.1431007095000@Atlassian.JIRA>
 <JIRA.12828017.1431007095057@arcas>
Subject: [jira] [Created] (AMBARI-10997) Improve Error Handling - hive view
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Erik Bergenholtz created AMBARI-10997:
-----------------------------------------

             Summary: 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


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)