[
https://issues.apache.org/jira/browse/DRILL-5391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15946874#comment-15946874
]
Arina Ielchiieva commented on DRILL-5391:
-----------------------------------------
Zelaine, regarding the decision, with CTTAS introduction approach for creating
files in Drill has changed, since we had to distinguish which files are
temporary and which are not. Writers were not aware which files they created
(fs.create(fileName)). To make solution configurable was decided to pass
permission which should be applied to the folder rather that indicating if this
is temp files or not (so if permission needs to be changed for some reason, it
would be easily maintained). Having permission 755 / 644 for persistent files
is common permission among systems and applications. Having this permission for
Drill did not seem to break the anything at that time (well, I guess this Jira
use case proves we were wrong).
I think it a good idea for Drill to create files with permission (like it's
done in Hive), though I guess to make this option configurable is what we have
missed. For example, for views Drill also creates files with specified
permission and it can be configurable.
> CTAS: folder and file permission should be 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
> Priority: Minor
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
