This content has been marked as final. Show 5 replies
In general, any set of operations that modifies or deletes many different major key paths will be expensive, because it operates on many (or all) nodes in the system. The example clears the entire store this way to make the example simpler, and the warning is because we don't expect apps to use that approach.
No, there is currently no bulk delete operation. This FAQ describes one approach:
Could you please describe your use case for bulk deletion, so we can keep it in mind as we go forward?
Thanks for your reply.
I am, as an Oracle RDBMS dba, just looking into the NoSql database to see how it works.
The example mentions that the iterative delete is not realistic. That made wonder if there are more efficient
Perhaps it is just 'works as designed' and is the iterative delete fine.
I do not know whether a bulk delete would be appropriate for the use that NoSQL is designed for.
On the other hand, if it is possible to implement a bulk delete in any form then why not?
A bulk delete is definitely something we would like to consider in the future, but for us it is all about prioritizing. :-) That's why I wondered if you had a specific use case in mind -- would you need to delete all data in the store (which I would see as a future admin function), or all records with a specific key prefix, etc?
I would expect that it would be able to remove all entries of a certain type.
Since the data in NoSQL can be of any kind I think it would be good if all the data belonging to a certain type.
So that would be : delete all the entries with major part '/user'.
And also delete all the entries of entries with major part '/email@example.com/'
Thanks for the feedback.
So that would be : delete all the entries with major part '/user'.This is currently done as described in the FAQ, and we may add bulk delete alternatives in the future.
And also delete all the entries of entries with major part '/firstname.lastname@example.org/'This is currently done efficiently with KVStore.multiDelete.