You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Zsolt Herczeg (JIRA)" <ji...@apache.org> on 2018/10/11 15:05:00 UTC
[jira] [Created] (IMPALA-7695) Consolidate ACL inheritance
Zsolt Herczeg created IMPALA-7695:
-------------------------------------
Summary: Consolidate ACL inheritance
Key: IMPALA-7695
URL: https://issues.apache.org/jira/browse/IMPALA-7695
Project: IMPALA
Issue Type: Improvement
Reporter: Zsolt Herczeg
As of now Impala behavior is not consistent regarding ACL inheritance by default.
If --insert_inherit_permissions is not specified, then:
{code:java}
CREATE EXTERNAL TABLE acl_test (a int) partitioned by (b int) STORED AS PARQUET LOCATION '/dataroot/acl_test/';
{code}
This will create the table directory (/dataroot/acl_test), and inherit the parent dir (/dataroot) acls.
{code:java}
ALTER TABLE acl_test ADD PARTITION (b=10)
{code}
This will create the partition directory (/dataroot/acl_test/b=10) and inherit the parent dir (/dataroot/acl_test) acls.
{code:java}
INSERT INTO acl_test (a,b) VALUES (1,2)
{code}
This will create the partition directory (/dataroot/acl_test/b=2) but will *not* inherit any acls.
The difference in the INSERT/ALTER behavior will lead to inconsistent partition directory permissions, depending on whether they were created explicitly beforhand or implicitly during an insert.
This is documented, but generally unexpected. I'd recommend to review if a more consistent approach could be followed for ACLs on partition directories..
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org