demo_vector_text

Source: crates/dynomite-search/examples/demo_vector_text.rs -- run with cargo run -p dynomite --example demo_vector_text

What it demonstrates

The library side of the RediSearch-compatible FT.* surface: creating an index, inserting documents, and running vector-similarity, text, and combined searches. It renders each request and its RESP reply so you can see the wire shapes even though the calls go through the registry rather than a socket.

#![allow(unused)]
fn main() {
use dynomite_search::ft::{self, FtOutcome, InfoValue};
use dynomite_search::registry::VectorRegistry;
use dyntext::index::TextIndex;

// FT.CREATE myidx ON HASH PREFIX 1 docs: SCHEMA ...
//   a 4-dimensional cosine-similarity HNSW vector field, plus text fields
// FT.ADD / HSET the documents
// FT.SEARCH with a KNN vector query, a text query, and a combination
}

Vectors are converted to little-endian bytes -- the exact format Redis Stack clients send for VECTOR fields -- so the example doubles as documentation of that encoding:

#![allow(unused)]
fn main() {
fn f32_to_le_bytes(values: &[f32]) -> Vec<u8> {
    let mut out = Vec::with_capacity(values.len() * 4);
    for v in values { out.extend_from_slice(&v.to_le_bytes()); }
    out
}
}

Design decisions and trade-offs

Library, not wire

The example calls the FT.* registry directly. This is the same API dynomited's dispatcher uses once a request is parsed, so it exercises the real search engine while staying independent of the network stack.

HNSW for vectors

The vector field uses an HNSW index with cosine similarity. HNSW trades a little index-build cost and memory for fast approximate nearest-neighbor search at query time.

Trigram text index

Text search is trigram-based, which supports substring and fuzzy matching without a full inverted-index-per-term structure.

When to use this pattern

When you want to understand or test the FT.* semantics -- index creation, the vector byte encoding, query construction -- without a running server. It is the fastest way to see what a given FT.SEARCH returns.

Where to go next

• Tutorial: Vector, Text, and Regex Search does the same thing over valkey-cli against a running dynomited.
• Full-Text, Vector, and Regex Search is the reference for the FT.* surface.
• quickstart drops to the vector store alone.