[
https://issues.apache.org/jira/browse/HBASE-20605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16493971#comment-16493971
]
Sean Busbey commented on HBASE-20605:
-------------------------------------
It would be good to have a check somewhere to warn about FS that won't behave
as expected in master/branch-2 as well. Maybe something to do on init of the
FileSystem overlay we do, rather than during a permission check.
Also we could do this as a whitelist of things that we've tested to work as
expected rather than a blacklist, since we'd just be doing a WARN / INFO
message.
> 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,
> HBASE-20605.002.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)
