mirror of
https://github.com/qdrant/qdrant.git
synced 2026-08-02 16:10:58 -05:00
eadf071a9c
The WAL is only truncated past operations whose segment flush was confirmed, so first_index is a durable lower bound on the applied sequence. The persisted applied_seq can legitimately lag behind it by more than one save interval: it is saved every 64 update-worker calls from a counter that restarts at zero on process start, and synchronous WAL replay never feeds it. A replay target computed from such a stale applied_seq can then sit before first_index, tripping the debug_assert from #8454 (flaky model_testing gate, #9844) and, in release builds, enqueueing already-truncated indices that fail with spurious "Operation not found in WAL" errors. Clamp the replay target at first_index: nothing before it ever needs replay. Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Collection
Crate, which implements all functions required for operations with a single collection of points. Points within a collection should share the same payload schema and have same vector size. So that search requests could be performed over all points of a single collection.
Structure
Update process
