[
https://issues.apache.org/jira/browse/HADOOP-14038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15905605#comment-15905605
]
John Zhuge commented on HADOOP-14038:
-------------------------------------
Discovered an issue related to the deprecation of ADLS properties (stored in
core-site.xml) in Patch 005:
* Configuration.addDeprecations is called in AdlFileSystem static initializer
* The {{conf}} passed into {{AdlFileSystem#initialize}} is constructed in
FsShell before AdlFileSystem static initializer is called
Thus, a simple command {{hadoop fs -ls adl://}} fails with Patch 005.
[~aw], [~ste...@apache.org], and [~cnauroth], is it ok to call
{{conf.reloadConfiguration()}} in {{AdlFileSystem#initialize}}? It fixes the
issue but means reloadConfiguration is called for every new instance. Is there
a better solution?
> Rename ADLS credential properties
> ---------------------------------
>
> Key: HADOOP-14038
> URL: https://issues.apache.org/jira/browse/HADOOP-14038
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/adl
> Affects Versions: 3.0.0-alpha3
> Reporter: John Zhuge
> Assignee: John Zhuge
> Priority: Minor
> Attachments: HADOOP-14038.001.patch, HADOOP-14038.002.patch,
> HADOOP-14038.003.patch, HADOOP-14038.004.patch, HADOOP-14038.005.patch
>
>
> Add ADLS credential configuration properties to {{core-default.xml}}.
> Set/document the default value for
> {{dfs.adls.oauth2.access.token.provider.type}} to {{ClientCredential}}.
> Fix {{AdlFileSystem#getAccessTokenProvider}} which implies the provider type
> is {{Custom}}.
> Fix several unit tests that set {{dfs.adls.oauth2.access.token.provider}} but
> does not set {{dfs.adls.oauth2.access.token.provider.type}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
