-
Notifications
You must be signed in to change notification settings - Fork 569
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
feat: deprecate legacy s3 connector #16337
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about just refuse the requests for s3 connector and tell them use s3_v2 instead.
A little bit weird but OK for the short-term.
cc @BugenZhao as introducing new item in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think main-cron ci tests will fail. Perhaps you will want to remove them.
maid cron failed on an irrelevant hummock test, merging now |
* deprecate legacy s3 connector ref risingwavelabs/risingwave#16337 * Update ingest-from-s3.md * update 1.9 ver --------- Co-authored-by: Shanlan(Lily) <150168166+ShanlanLi@users.noreply.github.com>
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
resolve #16234
Checklist
./risedev check
(or alias,./risedev c
)Documentation
Edited by @neverchanje
The only available s3 connector is now
s3_v2
.s3
is deprecated and should not appear in the document.