[
https://issues.apache.org/jira/browse/HBASE-11481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055833#comment-14055833
]
Hudson commented on HBASE-11481:
--------------------------------
SUCCESS: Integrated in HBase-0.98-on-Hadoop-1.1 #362 (See
[https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/362/])
HBASE-11481 TableSnapshotInputFormat javadoc wrongly claims HBase 'enforces
security' (apurtell: rev f2d8c1aa4134cd6fb29fa8aa05b66509782e9f01)
*
hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/TableSnapshotInputFormat.java
> TableSnapshotInputFormat javadoc wrongly claims HBase "enforces security"
> -------------------------------------------------------------------------
>
> Key: HBASE-11481
> URL: https://issues.apache.org/jira/browse/HBASE-11481
> Project: HBase
> Issue Type: Bug
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Priority: Minor
> Fix For: 0.99.0, 0.98.4, 2.0.0
>
> Attachments: HBASE-11481.patch
>
>
> In the Javadoc for TableSnapshotInputFormat, we have this:
> {quote}
> HBase also enforces security because all the requests are handled by the
> server layer, and the user cannot read from the data files directly.
> {quote}
> The snapshot input format operates on HFiles directly, that's how it gains
> its performance benefits. No requests are handled by the 'server layer'.
> Later the Javadoc correctly states the implications:
> {quote}
> Note that, given other users access to read from snapshot/data files will
> completely circumvent the access control enforced by HBase.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
