-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Cherry-pick namespace aware drop data #8511
Conversation
|
f0932d6
to
2a123f2
Compare
4dbaf51
to
1335343
Compare
5c3c1ad
to
4de6abf
Compare
5372973
to
b8b51d2
Compare
4de6abf
to
582abcc
Compare
582abcc
to
a7a4a5d
Compare
5b56acb
to
4a58b2d
Compare
4a58b2d
to
992ef57
Compare
96cb23c
to
965f318
Compare
0962011
to
c06c19d
Compare
965f318
to
faa405e
Compare
c06c19d
to
e08c643
Compare
faa405e
to
75fd407
Compare
e08c643
to
b942479
Compare
75fd407
to
de333d9
Compare
b942479
to
e66d8ec
Compare
de333d9
to
18154c7
Compare
e66d8ec
to
69dac5f
Compare
18154c7
to
371a2c1
Compare
69dac5f
to
6008c41
Compare
371a2c1
to
45a5ec1
Compare
6008c41
to
4e1118c
Compare
cherry-picks: * 260a789: This commit makes DropData namespace-aware in a multi-tenant system. Now, guardians of a namespace can call drop data on their namespace. Earlier only the guardian of the galaxy was allowed to do cluster-wide drop operation. * 7981a4d: use galaxynamespace when restore from old backup
4e1118c
to
6c16b0b
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.
Lets add some tests for restore flow also. For now, we can just add it in the list of tests.
fixes #8521