-
Notifications
You must be signed in to change notification settings - Fork 590
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(meta): support drop creating materialized views for v2 backend #17503
Conversation
ad984d3
to
c71f181
Compare
aa94636
to
f45f741
Compare
eaa467c
to
db45d28
Compare
Bump |
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.
############## Test drop foreground mv | ||
onlyif can-use-recover | ||
system ok | ||
psql -h localhost -p 4566 -d dev -U root -c 'create materialized view m1 as select * from t;' & |
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.
This doesn't work under parallelism execution since the database name won't be dev
anymore. 😕
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.
Parallel execution won't run this test. Because trigger recovery in one test thread will affect the execution of another test thread.
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.
Can use ./risedev psql -c
Bump |
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.
Not quite familiar with the meta part, may forward to @yezizp2012 for better insights. 🥺 Rest LGTM
############## Test drop foreground mv | ||
onlyif can-use-recover | ||
system ok | ||
psql -h localhost -p 4566 -d dev -U root -c 'create materialized view m1 as select * from t;' & |
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.
Can use ./risedev psql -c
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, seems like risedev-env
is not set correctly.
[cargo-make] INFO - Execute Command: "/usr/bin/env" "bash" "/tmp/fsio_0TY8YHlAuc.sh" "-c" "create materialized view m1 as select * from t;"
risedev-env file not found. Did you start cluster using./risedev d
or./risedev p
?
mkdir -p .risingwave/config | ||
cat <<EOF > .risingwave/config/risedev-env | ||
RW_META_ADDR="http://127.0.0.1:5690" | ||
RISEDEV_RW_FRONTEND_LISTEN_ADDRESS="127.0.0.1" | ||
RISEDEV_RW_FRONTEND_PORT="4566" | ||
EOF |
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 would suggest doing this in the playground
binary so that developers can also benefit from it locally. This is to address #17090. Can do it in next PRs.
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.
Good idea.
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Closes #14471
Notify catalog to fe in the following places:
Similar to #17484. See that PR's description for further details.
Main difference between v1 and v2 is that in v2 we report all catalogs to fe. Because all catalogs are immediately committed.
But we don't do the same for v1 yet, since for v1, only MVs' catalogs are immediately committed.
Checklist
./risedev check
(or alias,./risedev c
)Documentation
Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.