[
https://issues.apache.org/jira/browse/HBASE-5526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13223540#comment-13223540
]
Jesse Yates commented on HBASE-5526:
------------------------------------
Side note for other interested parties - just using dfs.umaskmode from hadoop
isn't sufficient here as we want to protect the data files, but still see the
directory structure. In true posix style, hdfs just applies the umask to all
the files _and_ directories, as opposed to differentiating between the two.
> 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.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
