-
Notifications
You must be signed in to change notification settings - Fork 612
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: support cross-db query in frontend and meta #20261
Conversation
008d2e7
to
745894e
Compare
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.
Rest LGTM!
We may need more tests for recovery, scale and background ddl. Not necessary to include in this PR.
Hi, there. 📝 Telemetry Reminder:
|
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.
LGTM!
Shall we add a release note to announce this new feature, and mention that currently user need to create a subscription on the table and should not drop the subscription?
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Related #19631 .
create_mv
, andcreate_sink
.CONNECT
privilege for cross-db query.Checklist
Documentation
Release note
Support cross-db query for both batch and streaming. The current requirements include:
There is at least one subscription created on the upstream table or materialized view.
The user is super or has connect permissions for the upstream databases and must also have the corresponding relation's query permissions.