[
https://issues.apache.org/jira/browse/HBASE-20605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16482733#comment-16482733
]
Josh Elser commented on HBASE-20605:
------------------------------------
Thanks for the explanation, Stack. Wasn't sure if I was just being dense.
{quote}I do like your improvement on my comment though, of how viewfs over
other than hdfs will mess us up too.... with its masking.
{quote}
Ok. Yeah, I think this is a fundamental issue that is missed how this hack
currently works. I can't think of an effective way to handle this (I don't
think there is API to know the real FS for some viewfs path). Maybe the
solution is to add viewfs to this list of schemas to ignore – it's not a "fix"
by any stretch but it might be the best we can do..
> Exclude new Azure Storage FileSystem from SecureBulkLoadEndpoint permission
> check
> ---------------------------------------------------------------------------------
>
> Key: HBASE-20605
> URL: https://issues.apache.org/jira/browse/HBASE-20605
> Project: HBase
> Issue Type: Improvement
> Components: security
> Reporter: Josh Elser
> Assignee: Josh Elser
> Priority: Major
> Fix For: 1.5.0, 1.3.3, 1.4.5
>
> Attachments: HBASE-20605.001.branch-1.patch
>
>
> Some folks in Hadoop are working on landing a new FileSystem from the Azure
> team: HADOOP-15407
> At present, this FileSystem doesn't support permissions which causes the
> SecureBulkLoadEndpoint to balk because it the staging directory doesn't have
> the proper 711 permissions.
> We have a static list of FileSystem schemes which we ignore this check on. I
> have a patch on an HBase 1.1ish which:
> # Adds the new FileSystem scheme
> # Makes this list configurable for the future
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
