Expand description
Vector subsystem.
This module is the in-process home of the Redis-Stack-style
RediSearch FT.* command surface. The architecture decision
lives in docs/dynvec/fold-into-redis-path.md; the short
version is:
- The
dynveccrate provides the per-table storage + HNSW index engine. - This module wraps each registered index in a
VectorTableand tracks them in aVectorRegistry. - The Redis parser recognises FT.* commands and routes them through this registry (Phase C, follow-up work).
- Distributed k-NN queries are coordinated by the
query_fsmstate machine, which fans out to every primary peer covering the index’s key range and merges the per-peer top-K replies.
Phase B (this commit) lands the registry, the schema
types, and the moved query coordinator. The FT.* command
parser, the cluster-machinery integration in
query_fsm, and the deprecation of the standalone
[dynvec::api] HTTP surface are each follow-up work.
Re-exports§
pub use registry::RegistryError;pub use registry::VectorRegistry;pub use registry::VectorTable;pub use registry::VectorTableInfo;pub use schema::DistanceMetric;pub use schema::IndexAlgorithm;pub use schema::MetadataField;pub use schema::MetadataFieldType;pub use schema::VectorSchema;pub use schema::VectorType;