Luis Cossío

Supersedes #3652, same thing but now event-based Tracked in #3471 Needs #4139 This PR determines to have too many collections when all of the following are true: - It has...

Needs #4209 Still some partial implementation for shard handling of query requests: - Adds a new `query()` required method on the `ShardOperation` trait, which receives the `ShardQueryRequest` type. - Includes...

Needs #4198 Future-proofs the grpc query vector type to allow any shape of vector. - `RawVector`: Only bare vector shapes - `VectorInput`: Can include point ids ### All Submissions: *...

Main idea: Each user request will be converted into a new type at each step of the search: API -> ToC -> Collection -> Shards. This PR adds the types...

- Introduces a `QueriedPoint` struct, which is equivalent to a `ScoredPoint`, but has a `Score` enum, which can be used to be the output of scroll-like requests, like when specifying...

universal-query: user-facing gRPC and REST request types

3

- Add gRPC `QueryPoints` type - Move `Fusion` to `points.proto` - Add rest `QueryRequest` type in collection. Not in `api::rest` because it needs types from `collection` crate. - Not added...

Review suggestion for #4301

Needs #4303 - [x] from REST - [x] from gRPC

Supersedes #4510 Fixes same issue as #4510, but now this is what I consider a proper fix. Now the resolver knows which way to order.

universal-query: Add farthest query

3

Adds a `{ query: { farthest: vector_input } }` shorthand for `{query: { recommend: { negative: [vector_input], strategy: "best_score" } } }` for better discoverability of features