[
https://issues.apache.org/jira/browse/HDFS-12404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yongjun Zhang updated HDFS-12404:
---------------------------------
Description:
HDFS-12357 introduced a new config
'dfs.namenode.inode.attributes.provider.bypass.users' to allow configured
users to bypass external attributes provider. However, after committing
HDFS-12357, noticed that a different config name
'dfs.namenode.authorization.provider.bypass.users' is put into
hdfs-default.xml, which is different than what used in java code. And this is
not correct.
Creating this jira to fix the hdfs-default.xml one to be consistent with the
implementation
was:
HDFS-12357 introduced a new config
'dfs.namenode.authorization.provider.bypass.users' to allow users to skip
external attributes provider totally. Name of the config needs to be
'dfs.namenode.inode.attributes.provider.bypass.users' for correctness purposes
and to align with the existing config
'dfs.namenode.inode.attributes.provider.class'.
> Rename hdfs config authorization.provider.bypass.users to
> attributes.provider.bypass.users
> ------------------------------------------------------------------------------------------
>
> Key: HDFS-12404
> URL: https://issues.apache.org/jira/browse/HDFS-12404
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs
> Affects Versions: 3.0.0-beta1
> Reporter: Yongjun Zhang
> Assignee: Manoj Govindassamy
> Fix For: 3.0.0-beta1
>
> Attachments: HDFS-12404.01.patch
>
>
> HDFS-12357 introduced a new config
> 'dfs.namenode.inode.attributes.provider.bypass.users' to allow configured
> users to bypass external attributes provider. However, after committing
> HDFS-12357, noticed that a different config name
> 'dfs.namenode.authorization.provider.bypass.users' is put into
> hdfs-default.xml, which is different than what used in java code. And this is
> not correct.
> Creating this jira to fix the hdfs-default.xml one to be consistent with the
> implementation
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
