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

Ashutosh Chauhan commented on HIVE-16346:
-----------------------------------------

I doubt the usability of {{hive.warehouse.subdir.inherit.perms}} in modern 
Hive. This flag was added in ancient times when Hive used to run in client mode 
via cli and inheriting perms was useful in that security model. Now that most 
(almost all?) deployments use HS2 and enforce the security via plugin (like 
Sentry, Ranger etc) this feature seems like obsolete for *all* filesystems. 
Shall we just delete this feature on master?

> inheritPerms should be conditional based on the target filesystem
> -----------------------------------------------------------------
>
>                 Key: HIVE-16346
>                 URL: https://issues.apache.org/jira/browse/HIVE-16346
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Sahil Takiar
>            Assignee: Sahil Takiar
>         Attachments: HIVE-16346.1.patch, HIVE-16346.2.patch, 
> HIVE-16346.3.patch, HIVE-16346.4.patch
>
>
> Right now, a lot of the logic in {{Hive.java}} attempts to set permissions of 
> different files that have been moved / copied. This is only triggered if 
> {{hive.warehouse.subdir.inherit.perms}} is set to true.
> However, on blobstores such as S3, there is no concept of file permissions so 
> these calls are unnecessary and can could a performance impact.
> One solution would be to set {{hive.warehouse.subdir.inherit.perms}} to 
> false, but this would be a global change that affects an entire HS2 instance. 
> So HDFS tables will no longer have permissions inheritance.
> A better solution would be to make the inheritance of permissions conditional 
> on the target filesystem.



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

Reply via email to