[
https://issues.apache.org/jira/browse/HADOOP-19681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18018863#comment-18018863
]
ASF GitHub Bot commented on HADOOP-19681:
-----------------------------------------
shameersss1 opened a new pull request, #7942:
URL: https://github.com/apache/hadoop/pull/7942
### Description of PR
S3A fails to initialize when S3 bucket namespace is having dot followed by a
number.
Specific Problem: URI parsing fails when S3 bucket names contain a dot
followed by a number (like bucket-v1.1-us-east-1). Java's
URI.getHost() method incorrectly interprets the dot-number pattern as a port
specification, causing it to return null.
### How was this patch tested?
Tested in us-east-1 with bucket having namespace with dot followed by a
number.
### For code changes:
- [x] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [x] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
> Fix S3A failing to initialize S3 buckets having namespace with dot followed
> by number
> -------------------------------------------------------------------------------------
>
> Key: HADOOP-19681
> URL: https://issues.apache.org/jira/browse/HADOOP-19681
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs/s3
> Reporter: Syed Shameerur Rahman
> Assignee: Syed Shameerur Rahman
> Priority: Major
>
> S3A fails to initialize when S3 bucket namespace is having dot followed by a
> number.
> {*}Specific Problem{*}: URI parsing fails when S3 bucket names contain a dot
> followed by a number (like {{{}bucket-v1.1-us-east-1{}}}). Java's
> URI.getHost() method incorrectly interprets the dot-number pattern as a port
> specification, causing it to return null.
>
> {{}}
> {code:java}
> hadoop dfs -ls s3a://bucket-v1.1-us-east-1/
> WARNING: Use of this script to execute dfs is deprecated.
> WARNING: Attempting to execute replacement "hdfs dfs" instead.
> 2025-09-08 06:13:06,670 WARN fs.FileSystem: Failed to initialize filesystem
> s3://bucket-v1.1-us-east-1/: java.lang.IllegalArgumentException: bucket is
> null/empty
> -ls: bucket is null/empty{code}
>
> {*}Please Note{*}: Although there has been discussion on not allowing S3
> buckets with such a namespace
> ([https://aws.amazon.com/blogs/aws/amazon-s3-path-deprecation-plan-the-rest-of-the-story/])
> , Amazon S3 still allows you to create a bucket with such a namespace.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
