stackabletech / stackabletech/trino-operator
Avoid non alphanumeric characters in S3 bucket names
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 63
- Forks
- 13
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 12
Description
This is just a reminder ticket.
When having a S3 bucket with underscore called demo_data, we receive a null pointer exception:
null uri host. This can be caused by unencoded / in the password string
In order to avoid that, bucket names should only use alphanumeric and dash characters e.g. demo-data.
This is a Java problem afaik.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named in the issue. Start by locating the S3 bucket-name handling and reproduce the reported failure with demo_data; done means bucket names follow the stated alphanumeric-and-dash constraint without producing the reported null pointer exception.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, java
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100