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

ASF GitHub Bot commented on HADOOP-19137:
-----------------------------------------

saxenapranav opened a new pull request, #6880:
URL: https://github.com/apache/hadoop/pull/6880

   jira: https://issues.apache.org/jira/browse/HADOOP-19137
   
   trunk pr: https://github.com/apache/hadoop/pull/6752
   
   Customer-provided-keys (CPK) configs are not allowed with 
non-hierarchal-namespace (non-HNS) accounts for ABFS. This patch aims to 
prevent ABFS initialization for non-HNS accounts if CPK configs are provided.




> [ABFS]Prevent ABFS initialization for non-hierarchal-namespace account if 
> Customer-provided-key configs given.
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-19137
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19137
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/azure
>    Affects Versions: 3.4.0
>            Reporter: Pranav Saxena
>            Assignee: Pranav Saxena
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.5.0
>
>
> Store doesn't flow in the namespace information to the client. 
> In https://github.com/apache/hadoop/pull/6221, getIsNamespaceEnabled is added 
> in client methods which checks if namespace information is there or not, and 
> if not there, it will make getAcl call and set the field. Once the field is 
> set, it would be used in future getIsNamespaceEnabled method calls for a 
> given AbfsClient.
> Since, CPK both global and encryptionContext are only for hns account, the 
> fix that is proposed is that we would fail fs init if its non-hns account and 
> cpk config is given.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to