-
Notifications
You must be signed in to change notification settings - Fork 594
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test other components that relying on S3-compatible storage #10995
Comments
This is a reminder from the past. Can you please help with this once S3 source & sink completed? cc. @tabVersion @xiangjinwu |
This issue has been open for 60 days with no activity. If you think it is still relevant today, and needs to be done in the near future, you can comment to update the status, or just manually remove the You can also confidently close this issue as not planned to keep our backlog clean. |
Already mentioned in #8266.
For storage, I guess it generally works, and we just want to test maturity https://github.com/risingwavelabs/risingwave-test/issues/285.
But I guess other components are not tested yet, as it's not functional, e.g., #10994.
Note that now each component has it own logic of AWS config handling, and they are inconsistent. This might be the root of the problems.
The text was updated successfully, but these errors were encountered: