10000
meta fails to parse bucket name containing dot (.) #22044
Labels
type/bug
Type: Bug. Only for issues.
Milestone
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
When using S3 as state store, with an S3 bucket name that contains a dot (.), the meta-node panics with a
ConfigInvalid
error. However, S3 bucket names with dots are valid according to naming rules. The same configuration works correctly when using a bucket name without dots.Error message/log
To Reproduce
If change to a bucket whose name does not contain dot, it works fine.
Expected behavior
No response
How did you deploy RisingWave?
No response
The version of RisingWave
risingwavelabs/risingwave:v2.4.0
Additional context
No response
The text was updated successfully, but these errors were encountered: