If it had some more intelligence it would not be a bad feature. The
alternative for users working with very large systems is complicated
scripting.
On Thu, May 11, 2023 at 4:09 AM Jan Høydahl wrote:
> I didn't know about this multi delete either, it must have been introduced
> for a reason? If y
I didn't know about this multi delete either, it must have been introduced for
a reason? If you e.g. want to reduce "replicationFactor" from 5 to 3, it will
not work to update collectionProp "replicationFactor", not even the individual
num props. That would be the natural way for this feature to
I didn't include the collection name in my abbreviated URL, but it is
a required parameter on DELETEREPLICA requests, yep.
Historically, DELETEREPLICA is covered by the "collection-admin-edit"
predefined permission, which is usually given to admins. Which is
consistent with our other cluster-topo
This sounds like something that should have some scoping criteria for
security (I haven't looked at code yet). Is it possible that User A be
given the ability to delete replicas for just a gien collection? (I don't
see the collection in the url you provided)
On Tue, May 9, 2023 at 1:19 PM Jason Ge
Hey all,
I was looking at /admin/collections?action=DELETEREPLICA recently and
was surprised to discover that the API is much more powerful than I'd
realized. Not only can it delete a single replica from a single
shard, but it can also be used to delete 'N' replicas from either a
single shard or
