You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Pranay Singh (JIRA)" <ji...@apache.org> on 2017/12/12 01:36:00 UTC
[jira] [Resolved] (IMPALA-4927) Impala should be able to handle
invalid input from Sentry
[ https://issues.apache.org/jira/browse/IMPALA-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pranay Singh resolved IMPALA-4927.
----------------------------------
Resolution: Resolved
The issue has been resolved by the below checkin
---------------------------------------------------------------------------
IMPALA-4927: Impala should handle invalid input from Sentry
Impala requests a list of roles from Sentry and then asks for privileges
for each role. If Sentry returns a non existent role in the first step,
then there will be a Java exception in Impala in the second step and
the communication with Sentry is aborted.
The issue is fixed by handling the exception if an invalid role is
found and continue with getting permissions for the rest of the roles.
Testing:
-------
Since invalid role could not be created through impala-shell/Hue
interface the code was instrumented to have an invalid Role " ",
and SHOW ROLES statement was executed from impala shell to see
how the condition is handled.
Change-Id: I781411018d580854d80a9cad81a1ded7ca16af8b
Reviewed-on: http://gerrit.cloudera.org:8080/8588
Reviewed-by: Alex Behm <al...@cloudera.com>
Reviewed-by: Zach Amsden <za...@cloudera.com>
Tested-by: Impala Public Jenkins
> Impala should be able to handle invalid input from Sentry
> ---------------------------------------------------------
>
> Key: IMPALA-4927
> URL: https://issues.apache.org/jira/browse/IMPALA-4927
> Project: IMPALA
> Issue Type: Bug
> Components: Catalog
> Affects Versions: Impala 2.9.0
> Reporter: Taras Bobrovytsky
> Assignee: Pranay Singh
> Labels: newbie
>
> Impala first requests a list of roles from Sentry and then asks for privileges for each role. If Sentry returns a non existent role in the first step, then there will be a Java exception in Impala in the second step and the communication with Sentry is aborted.
> Impala needs to be able to handle this situation more gracefully. For example, an error can be logged, but still try to get permissions for the rest of the roles.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)