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

Aman Sinha commented on IMPALA-10554:
-------------------------------------

COMPUTE STATS falls in the same category.

> Block modifications when row-filter/column-mask is enabled for the user
> -----------------------------------------------------------------------
>
>                 Key: IMPALA-10554
>                 URL: https://issues.apache.org/jira/browse/IMPALA-10554
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Security
>    Affects Versions: Impala 3.4.0
>            Reporter: Quanlong Huang
>            Priority: Critical
>         Attachments: column_masking_policy.png
>
>
> Per RANGER-1087 and RANGER-1100, table modifications(insert/delete/update) 
> should be blocked when row-filter/column-masking policy is enabled for the 
> user.
> Currently, Impala doesn't block them, which is a bug considering to Hive's 
> behavior.
> *Reproducing the issue*
>  Create a table and a column masking policy on it:
> {code:sql}
> hive> create table hql_tbl (id int, name string) stored as textfile;
> hive> insert into table hql_tbl values (0, 'aaa'), (1, 'bbb'), (2, 'ccc');
> {code}
> Column masking policy:
>  !column_masking_policy.png|width=534,height=572!
> In Hive, the INSERT will be denied:
> {code:sql}
> hive> insert into table hql_tbl values (3, 'ddd');
> Error while compiling statement: FAILED: HiveAccessControlException 
> Permission denied: user [admin] does not have [UPDATE] privilege on 
> [default/hql_tbl]
> {code}
> However, the user is able to insert values using Impala.
> The related Ranger config is 
> xasecure.hive.block.update.if.rowfilter.columnmask.specified.
> CC [~fangyurao]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org

Reply via email to