You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Dongjoon Hyun (Jira)" <ji...@apache.org> on 2020/02/12 22:36:00 UTC

[jira] [Updated] (SPARK-30797) Set tradition user/group/other permission to ACL entries when setting up ACLs in truncate table

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

Dongjoon Hyun updated SPARK-30797:
----------------------------------
    Affects Version/s: 2.4.5

> Set tradition user/group/other permission to ACL entries when setting up ACLs in truncate table
> -----------------------------------------------------------------------------------------------
>
>                 Key: SPARK-30797
>                 URL: https://issues.apache.org/jira/browse/SPARK-30797
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 2.4.5, 3.0.0
>            Reporter: L. C. Hsieh
>            Assignee: L. C. Hsieh
>            Priority: Major
>             Fix For: 3.0.0
>
>
> This is a follow-up to the SPARK-30312. In SPARK-30312, the patch proposed to preserve path permission when truncating table. When setting up original ACLs, we need to set user/group/other permission as ACL entries too, otherwise if the path doesn't have default user/group/other ACL entries, ACL API will complain an error Invalid ACL: the user, group and other entries are required.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org