[ 
https://issues.apache.org/jira/browse/IMPALA-8530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16838933#comment-16838933
 ] 

ASF subversion and git services commented on IMPALA-8530:
---------------------------------------------------------

Commit cc78b764e85503e26f3eb37bdcf5df50c0cc6484 in impala's branch 
refs/heads/master from Fredy Wijaya
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=cc78b76 ]

IMPALA-8530: Return more user friendly error messages on unsupported SQL

This patch updates the error messages to return more friendly error
messages for the unsupported SQL statements when running with Sentry or
Ranger to improve user experience. This patch tries to differentiate
between UnsupportedOperationException, which is an internal exception to
indicate a programming error vs UnsupportedFeatureException, which is
an exception that will be exposed to the users to indicate that a
feature is not supported.

Testing:
- Added tests for unsupported SQL
- Ran FE tests
- Ran E2E authorization tests

Change-Id: Icf08ee9e1a83d7597811b1c8585aee5872d0baaf
Reviewed-on: http://gerrit.cloudera.org:8080/13295
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>


> Make some unsupported SQL error messages to be more user friendly
> -----------------------------------------------------------------
>
>                 Key: IMPALA-8530
>                 URL: https://issues.apache.org/jira/browse/IMPALA-8530
>             Project: IMPALA
>          Issue Type: Sub-task
>          Components: Frontend
>            Reporter: Fredy Wijaya
>            Assignee: Fredy Wijaya
>            Priority: Critical
>
> Some error messages, such as running "SHOW ROLES" with Ranger aren't very 
> user friendly. We need to fix those error messages for unsupported SQL 
> commands.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to