Deleting points removes selected records from an existing collection. The collection remains available, so its vector configuration, payload indexes, and other collection-level schema remain in place for subsequent writes and searches.

Deleting a collection is a much larger operation: it removes the collection and its stored data, and therefore the collection's vector configuration and indexes disappear with it. Recreating it requires defining the vector configuration and rebuilding any required indexes or data.

The trade-off is targeted cleanup versus destructive reset. Point deletion is appropriate for normal lifecycle events, while collection deletion is typically used for deliberate teardown, migrations, or rebuilding a dataset.

A common mistake is treating collection deletion as a fast way to clear stale points without considering recovery. It is destructive, so I would require explicit operational safeguards and verify that the collection can be reconstructed from a source of truth.

javascript

1
Point deletion preserves the collection schema and configuration
2
Collection deletion removes the collection's data and configuration
3
Recreating a collection requires restoring its vector configuration and indexes
4
Treat collection deletion as a destructive administrative operation

Difficulty: 3/10

Topics: Collections, Point deletion, Collection deletion

Scenario Questions

0-2 years experience

1
You need to remove one customer's documents but keep all other tenants searchable. Would you delete the collection? Why not?
2
A developer deletes a collection expecting to remove only its current points. What additional state is lost?

2-5 years experience

1
You need to rebuild all embeddings using a new model. Why might creating a new collection be safer than deleting the existing one first?
2
A cleanup job accidentally deletes an entire collection in production. What recovery information would you need?

5-8 years experience

1
You need to migrate a large collection to a new vector configuration with minimal downtime. How would you use parallel collections to reduce migration risk?
2
A collection contains expensive payload indexes that take significant time to rebuild. How does that affect your decision between point deletion and collection recreation?

8+ years experience

1
You need a zero-downtime reindex of a critical Qdrant dataset. How would you design collection creation, backfill, validation, and traffic cutover?
2
An engineer proposes periodically deleting and recreating production collections to control storage fragmentation. What operational and recovery risks would you evaluate?

Follow-up Questions

❓Why is collection deletion more disruptive than deleting all points?
❓How would you safely rebuild a collection from a source of truth?