hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "genericqa (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-14565) Azure: Add Authorization support to ADLS
Date Mon, 04 Dec 2017 15:11:01 GMT

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

genericqa commented on HADOOP-14565:
------------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  0s{color} | {color:blue}
Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  4s{color} | {color:red}
HADOOP-14565 does not apply to trunk. Rebase required? Wrong Branch? See https://wiki.apache.org/hadoop/HowToContribute
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HADOOP-14565 |
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12880108/HADOOP_14565__Added_authorizer_functionality_to_ADL_driver.patch
|
| Console output | https://builds.apache.org/job/PreCommit-HADOOP-Build/13778/console |
| Powered by | Apache Yetus 0.7.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> Azure: Add Authorization support to ADLS
> ----------------------------------------
>
>                 Key: HADOOP-14565
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14565
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/adl
>    Affects Versions: 2.8.0
>            Reporter: Ryan Waters
>            Assignee: Sivaguru Sankaridurg
>         Attachments: HADOOP_14565__Added_authorizer_functionality_to_ADL_driver.patch
>
>
> This task is meant to add an Authorizer interface to be used by the ADLS driver in a
similar way to the one used by WASB. The primary difference in functionality being that the
implementation of this Authorizer will be provided by an external jar. This class will be
specified through configuration using "adl.external.authorization.class". 
> If this configuration is provided, an instance of the provided class will be created
and all file system calls will be passed through the authorizer, allowing implementations
to determine if the file path and access type (create, open, delete, etc.) being requested
is valid. If the requested implementation class is not found or it fails to initialize, it
will fail initialization of the ADL driver. If no configuration is provided, calls to the
authorizer will be skipped and the driver will behave as it did previously.  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org


Mime
View raw message