[HADOOP-19208] ABFS: Fixing logic to determine HNS nature of account to avoid extra getAcl() calls

• Type: Sub-task
• Status: Patch Available
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.4.0
• Component/s: fs/azure
• Target Version/s: 3.5.0, 3.4.1
• Assignee: Anuj Modi
• Reporter: Anuj Modi
• Created: 19/Jun/24 16:56
• Updated: 20/Jun/24 14:58

Description

ABFS driver needs to know the type of account being used. It relies on the user to inform the account type using the config `fs.azure.account.hns.enabled`.
If not configured, driver makes a getAcl call to determine the account type.

Expectation is getAcl() will fail with 400 Bad Request if made on the FNS Account.
For any other case including 200, 404 it will indicate account is HNS.

Today, when determining this, the logic only checks status code to be either 200 or 400. In case of 404, nothing is inferred, and this leads to more getAcl again and again until 200 or 400 comes.

Fix is to update the logic such that if getAcl() fails with 400, it is FNS account. For all other cases it will be an HNS account. In case of throttling, if all retries are exhausted, FS init itself will fail.

This is also to fix a test case failing on trunk. testGetAclCallOnHnsConfigAbsence(org.apache.hadoop.fs.azurebfs.ITestAzureBlobFileSystemInitAndCreate)