[ 
https://issues.apache.org/jira/browse/HADOOP-17589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18042654#comment-18042654
 ] 

ASF GitHub Bot commented on HADOOP-17589:
-----------------------------------------

github-actions[bot] commented on PR #2774:
URL: https://github.com/apache/hadoop/pull/2774#issuecomment-3609383079

   We're closing this stale PR because it has been open for 100 days with no 
activity. This isn't a judgement on the merit of the PR in any way. It's just a 
way of keeping the PR queue manageable.
   If you feel like this was a mistake, or you would like to continue working 
on it, please feel free to re-open it and ask for a committer to remove the 
stale tag and review again.
   Thanks all for your contribution.




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

Reply via email to