[ 
https://issues.apache.org/jira/browse/IMPALA-14751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Smith updated IMPALA-14751:
-----------------------------------
    Description: 
Newer versions of Hadoop will try to query a configured Azure tenant unless 
explicitly disabled. Our minicluster config sets several dummy Azure settings, 
which results in errors like
{code}
Invalid configuration value detected for fs.azure.account.hns.enabledStatus 
code: -1 error code: null error message: Auth failure: HTTP Error 400; 
url='https://login.microsoftonline.com/DummyAdlsTenantId/oauth2/token' ...
{code}

We should add {{fs.azure.account.hns.enabled=false}} to avoid this.

  was:Newer versions of Hadoop will try to query a configured Azure tenant 
unless explicitly disabled. Our minicluster config sets several dummy Azure 
settings, so we should add {{fs.azure.account.hns.enabled}} to avoid this.


> Avoid reaching out to Azure dummy tenant in minicluster
> -------------------------------------------------------
>
>                 Key: IMPALA-14751
>                 URL: https://issues.apache.org/jira/browse/IMPALA-14751
>             Project: IMPALA
>          Issue Type: Task
>            Reporter: Michael Smith
>            Assignee: Michael Smith
>            Priority: Major
>
> Newer versions of Hadoop will try to query a configured Azure tenant unless 
> explicitly disabled. Our minicluster config sets several dummy Azure 
> settings, which results in errors like
> {code}
> Invalid configuration value detected for fs.azure.account.hns.enabledStatus 
> code: -1 error code: null error message: Auth failure: HTTP Error 400; 
> url='https://login.microsoftonline.com/DummyAdlsTenantId/oauth2/token' ...
> {code}
> We should add {{fs.azure.account.hns.enabled=false}} to avoid this.



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