aws S3 streaming upload random naming strategy always overwrite the initial file (without suffix)
- Dominant language
- Java
- Stars
- 302
- Forks
- 232
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 114
Description
When choosing `namingStrategy(AWSS3NamingStrategyEnum.random)` and `restartingPolicy(AWSS3RestartingPolicyEnum.lastPart)`, the very first file without any UUID suffix is always overwritten when the application restarts. One would expect in this case it would start with a file with a new UUID suffix.
version:
```
2.11.0
2.11.1.Final
quarkus-bom
io.quarkus
2.11.1.Final
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at the AWSS3NamingStrategyEnum.random and AWSS3RestartingPolicyEnum.lastPart entry points and reproduce the behavior using the versions listed in the issue. Done means restarting no longer overwrites the initial unsuffixed file and instead begins a file with a new UUID suffix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, java
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100