[
https://issues.apache.org/jira/browse/HBASE-5526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13224039#comment-13224039
]
Jesse Yates commented on HBASE-5526:
------------------------------------
bq. Kinda nasty that the file operations now need a Configuration object
Indeed, but all the sources pretty much have it directly (or pretty close)
available. Thinking about adding a method that doesn't need one, but instead
just uses HBaseConfiguration.create() as its conf (which is what people are
probably going to do implicitly in the future without that overloaded method).
bq. Would probably not hardcode 022 as the default umask
This is the default umask that hadoop applies to files, so I figured it would
be fine as that. I feel like these conf values should be the defaults, but
maybe just wide open? Note that since 'hbase.files.permissions.enabled' -
should probably be renamed - is false, the default will be to use the
filesystem defaults and ignore the conf values (also stated in the description
of those params in the conf).
bq. Wanna put up RB?
Done.
> 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
