You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this case, just modify the stored parameters in the streaming plans
Does this mean users can do whatever they want as long as not changing the connector?
TBH, I vote for this behavior because it is hard to tell whether we should enforce clean state in some cases, eg. broker SSL cert expires and the broker is mounted to another domain. RisingWave cannot see the two broker_addrs as the same.
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 no-issue-activity label.
You can also confidently close this issue as not planned to keep our backlog clean.
Don't worry if you think the issue is still valuable to continue in the future.
It's searchable and can be reopened when it's time. 😄
ALTER TABLE/SOURCE <table name> CONNECTOR [CLEAN STATE] WITH (…)
CLEAN STATE
CLEAN STATE
, the user can change the table's connector.more informations here. https://risingwave-labs.slack.com/archives/C069EV2Q5MK/p1721982104476979?thread_ts=1721815617.574089&cid=C069EV2Q5MK
The text was updated successfully, but these errors were encountered: