[
https://issues.apache.org/jira/browse/HADOOP-17589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17802862#comment-17802862
]
Shilun Fan commented on HADOOP-17589:
-------------------------------------
Bulk update: moved all 3.4.0 non-blocker issues, please move back if it is a
blocker. Retarget 3.5.0.
> Support Custom Endpoint For Hadoop Azure working with Storage Emulator
> ----------------------------------------------------------------------
>
> Key: HADOOP-17589
> URL: https://issues.apache.org/jira/browse/HADOOP-17589
> Project: Hadoop Common
> Issue Type: Bug
> Components: hadoop-thirdparty
> Affects Versions: 3.3.0
> Reporter: Yaniv Ironi
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When using the Hadoop Azure library to write files using the wasb:// schema,
> and using the configuration for Hadoop Azure storage emulator
> (fs.azure.storage.emulator.account.name), The client assumes that the
> emulator will run on localhost with the default port.
> When writing ITs and using Test Containers, the emulator will run on a custom
> endpoint but there is no way to tell that for the client.
> The problem is in AzureNativeFileSystemStore.java, in connectUsingCredentials
> method,
> which runs:
> CloudStorageAccount account =
> CloudStorageAccount.getDevelopmentStorageAccount()
> Which will use the default localhost address.
> The fix is easy (And I already fixed it and tested it on my own environment,
> and I will PR the fix)
> CloudStorageAccount.getDevelopmentStorageAccounts has already an overload
> that accepts URI for a custom endpont, and we can use it.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
