This might be related to the Bulk export feature request, but still writing it here to explain our use case.
We have a production index but we also want to allow the development team to test and reproduce issues that occur in production. This is why we have 2 indexes production and dev index.
Every night, a backup job runs that does the following:
- Creates a collection from the production index
- Deletes and recreates the dev index from this collection
We noticed that the the deletion of collection is not a deterministic operation. The API returns the response immediately. We’ve added some waiting time but we still see jobs occasionally failing. The only thing we can add is polling the collection status until it is deleted which feels hacky.
What I’d like to have is one of these two:
- Delete collection endpoint should only return when the collection is actually deleted
- The create collection API should allow for the existing index to be overwritten. If we do this now, we always get an error collection already exists. We can pass an extra parameter to the endpoint something like
overwriteExistingCollection = True
If you know a better way of doing this, happy to hear about it. I feel having multiple indexes that sync between each other or allowing easy export/import between indexes is quite a common scenario.
Thanks