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 2018/01/04 01:03:17 UTC

[jira] [Resolved] (IMPALA-5998) Explain on view not allowed with column level privileges on underlying table

     [ https://issues.apache.org/jira/browse/IMPALA-5998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pranay Singh resolved IMPALA-5998.
----------------------------------
    Resolution: Cannot Reproduce

> Explain on view not allowed with column level privileges on underlying table
> ----------------------------------------------------------------------------
>
>                 Key: IMPALA-5998
>                 URL: https://issues.apache.org/jira/browse/IMPALA-5998
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Frontend
>    Affects Versions: Impala 2.9.0
>            Reporter: Jamison Bennett
>            Assignee: Pranay Singh
>              Labels: security
>
> I think there is a bug in the permissions checking for explaining a view.
> Steps to reproduce:
> {code}
> create role systest_role;
> grant role systest_role to group systest;
> create database test;
> create table test.employees (firstname string, lastname string, salary int);
> grant select(firstname,lastname) on table test.employees to role systest_role;
> insert into table test.employees (firstname, lastname, salary) values ("John", "Smith", 12345);
> create view test.employees_view as select firstname, lastname from test.employees;
> grant select on table test.employees_view to role systest_role;
> select * from test.employees_view;
> explain select * from test.employees_view;
> ERROR: AuthorizationException: User 'systest@GCE.CLOUDERA.COM' does not have privileges to EXPLAIN this statement.
> {code}
> I think the above explain should be authorized because the following equivalent explain is authorized:
> explain select * from (select firstname, lastname from test.employees) as q;



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)