You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2018/05/19 04:47:00 UTC

[jira] [Commented] (HBASE-20605) Exclude new Azure Storage FileSystem from SecureBulkLoadEndpoint permission check

    [ https://issues.apache.org/jira/browse/HBASE-20605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16481462#comment-16481462 ] 

Ted Yu commented on HBASE-20605:
--------------------------------

{code}
  private final static String[] FsWithoutSupportPermission = {"s3", "s3a", "s3n", "wasb", "wasbs", "swift"};
{code}
The above is the minimal set of file systems without permission support.
When reading from config, should the custom config value be added to this set ?

> 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)