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

Jesse Yates updated HBASE-5526:
-------------------------------

    Attachment: java_HBASE-5526-v2.patch

Attaching patch for general umask application for files and directories.

Essentially, the patch takes all the file and directory creation in src/main 
and pipes it through new methods in FSUtils, which automatically apply the file 
permissions if they are turned on, rather than just doing the straigh 
fs.create() or fs.mkdirs() calls.

Unfortunately, this is a wider sweeping change than anticipated as there are a 
lot of places that create files and directories. However, this helps centralize 
the code in the future, if we want to more/fancier stuff to the files.
                
> Optional file permission settings
> ---------------------------------
>
>                 Key: HBASE-5526
>                 URL: https://issues.apache.org/jira/browse/HBASE-5526
>             Project: HBase
>          Issue Type: New Feature
>          Components: regionserver
>            Reporter: Jesse Yates
>            Assignee: Jesse Yates
>             Fix For: 0.94.0
>
>         Attachments: java_HBASE-5526-v2.patch, java_HBASE-5526.patch
>
>
> Currently many all the files created by the HBase user are just written using 
> the default file permissions granted by hdfs. However, it is often times 
> adventageous to only allow a subset of the world to view the actual data 
> written by hbase when scanning the raw hdfs files. 
> This ticket covers setting permissions for files written to hdfs that are 
> storing actual user data, as opposed to _all_ files written to hdfs as many 
> of them contain non-identifiable metadata.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to