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 "Todd Lipcon (JIRA)" <ji...@apache.org> on 2018/08/15 03:36:00 UTC

[jira] [Commented] (IMPALA-7321) Write permissions checks for insert into multi-level partitioned table are incorrect

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

Todd Lipcon commented on IMPALA-7321:
-------------------------------------

Another data point against this: if the partition directories have ACLs, we need to do a round trip per directory. It seems that ACLs are quite common when features like Sentry "sync" are enabled, so these checks are quite slow.

> Write permissions checks for insert into multi-level partitioned table are incorrect
> ------------------------------------------------------------------------------------
>
>                 Key: IMPALA-7321
>                 URL: https://issues.apache.org/jira/browse/IMPALA-7321
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Frontend
>            Reporter: Todd Lipcon
>            Priority: Minor
>
> Currently, the logic to determine whether a table has write access is a bit incorrect: we check each existing partition, and we check the top-level location for the table. However, if a table uses partitioning on multiple levels, we could have the following situation:
> table/   (read-write)
> table/x=1/ (read-only)
> table/x=1/y=1/ (read-write)
> In this case, the table would pass the check and be determined to be "writable" but in fact an attempt to create a new partition such as x=1/y=2 would fail in the backend.



--
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