Open croffler opened 1 year ago
I just reproduced exactly this thing! The collection is NOT DELETED OS: Ubuntu Typesense version: 0.26
UPDATE: This "delete bug" is not easy to reproduce.I saw it trying to delete and than immediately to create collection with the same name. All in Java code, with Typesense Java API.
I have to say, I did A LOT of upserts into this collection before, during several days (experimented with Typesense over a week, importing almost the same documents many times, with slightly different schemas)
Now I changed the collection name -to be able to continue- and... looks like this bug is gone. There was no upserts/inserts into this new collection, and multiple delete collection+create worked
I will leave this issue open, but just want to add a note that:
client.collections("Countries").retrieve();
will NOT return null
value when the collection is not found. It will throw an ObjectNotFound
exception. So atleast for the original issue, checking for null
is wrong.
Description
Drop collection does not seem to completely remove the collection.
Steps to reproduce
Expected Behavior
Deleting an collection should drop the collection
Actual Behavior
After deleting a collection, the collection is not null, but when accessing it an exception is thrown
Metadata
Typesense Version: 0.24.1
OS:MacOs