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

Arina Ielchiieva updated DRILL-5391:
------------------------------------
    Description: 
In Drill 1.9, CREATE TABLE AS creates a folder with permissions 777, while on 
Drill 1.10, the same commands creates a folder with permission 775. Both drills 
are started with root user, installed on the same servers and accesses the same 
HDFS.

Scope:
Added new configuration option exec.persistent_table.umask which default to 002.
Default directory permission will be 775, file - 664.
User can modify this option on session or system level.
If umask was set incorrectly, default umask will be used (002) and error will 
be logged.

For example, if user wants to create table will full access to folders and 
files, he needs to update umask:
alter session set `exec.persistent_table.umask` = '000';
In this case folders will be created with 777 permission, files with 666.


  was:In Drill 1.9, CREATE TABLE AS creates a folder with permissions 777, 
while on Drill 1.10, the same commands creates a folder with permission 775. 
Both drills are started with root user, installed on the same servers and 
accesses the same HDFS.


> CTAS: make folder and file permission configurable
> --------------------------------------------------
>
>                 Key: DRILL-5391
>                 URL: https://issues.apache.org/jira/browse/DRILL-5391
>             Project: Apache Drill
>          Issue Type: Bug
>    Affects Versions: 1.9.0, 1.10.0
>         Environment: CentOS 7, HDP 2.4
>            Reporter: Chua Tianxiang
>            Assignee: Arina Ielchiieva
>            Priority: Minor
>              Labels: doc-impacting
>         Attachments: Drill-1-10.PNG, Drill-1-9.PNG
>
>
> In Drill 1.9, CREATE TABLE AS creates a folder with permissions 777, while on 
> Drill 1.10, the same commands creates a folder with permission 775. Both 
> drills are started with root user, installed on the same servers and accesses 
> the same HDFS.
> Scope:
> Added new configuration option exec.persistent_table.umask which default to 
> 002.
> Default directory permission will be 775, file - 664.
> User can modify this option on session or system level.
> If umask was set incorrectly, default umask will be used (002) and error will 
> be logged.
> For example, if user wants to create table will full access to folders and 
> files, he needs to update umask:
> alter session set `exec.persistent_table.umask` = '000';
> In this case folders will be created with 777 permission, files with 666.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to