alamb commented on PR #828:
URL: 
https://github.com/apache/arrow-rs-object-store/pull/828#issuecomment-5331872674

   I think this breaks hostname creation for s3 express
   
   Here is a reproducer that shows things working on main but broken with this 
change (the hostname the PR creates is invalid)
   
   
[object-store-dual-stack.zip](https://github.com/user-attachments/files/31190545/object-store-dual-stack.zip)
   
   
   ```shell
   cargo run 
   ...
   
   head() on s3_express bucket repro--use1-atl2-az1--x-s3 (Atlanta Local Zone, 
us-east-1)
   
   [main   ] error: Generic S3 error: Error performing CreateSession request: 
Error performing GET 
https://repro--use1-atl2-az1--x-s3.s3express-use1-atl2-az1.us-east-1.amazonaws.com/?session
 in 644.927084ms - Server returned non-2xx status code: 403 Forbidden: <?xml 
version="1.0" encoding="UTF-8"?>
   <Error><Code>InvalidAccessKeyId</Code><Message>The AWS Access Key Id you 
provided does not exist in our 
records.</Message><RequestId>019361178c0001a015f431a004001973ef4daba1</RequestId><HostId>2TG3D8a0ILee</HostId></Error>
   [main   ] root cause: Server returned non-2xx status code: 403 Forbidden: 
<?xml version="1.0" encoding="UTF-8"?>
   <Error><Code>InvalidAccessKeyId</Code><Message>The AWS Access Key Id you 
provided does not exist in our 
records.</Message><RequestId>019361178c0001a015f431a004001973ef4daba1</RequestId><HostId>2TG3D8a0ILee</HostId></Error>
   
   [PR #828] error: Generic S3 error: Error performing CreateSession request: 
Error performing GET 
https://repro--use1-atl2-az1--x-s3.s3express-use1-atl2-az1.dualstack.us-east-1.amazonaws.com/?session
 in 1.438584ms - HTTP error: error sending request
   [PR #828] root cause: failed to lookup address information: nodename nor 
servname provided, or not known
   ```


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

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to