[
https://issues.apache.org/jira/browse/HADOOP-17589?focusedWorklogId=565896&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-565896
]
ASF GitHub Bot logged work on HADOOP-17589:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 14/Mar/21 12:48
Start Date: 14/Mar/21 12:48
Worklog Time Spent: 10m
Work Description: iryaniv opened a new pull request #2774:
URL: https://github.com/apache/hadoop/pull/2774
HADOOP-17589 - Support Custom Endpoint For Hadoop Azure working with
Storage Emulator
Tested and worked with Azurite
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 565896)
Remaining Estimate: 0h
Time Spent: 10m
> 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.4.0
> Reporter: Yaniv Ironi
> Priority: Major
> Time Spent: 10m
> 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.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
