Help center assistants
Articles and resolved tickets are ingested with their product and language as metadata. Each answer is grounded in the right product's documentation.
Answer questions over your own documents with chunking, metadata filters, hybrid vector and keyword search, and cached rerank scores, in one engine.
One chunk per paragraph. Use your embedding model's dimensions (3 keeps the example short).
An animated walkthrough with real HotKV commands and example replies. Click any step to jump to it.
A retrieval pipeline usually means a vector database, a keyword index, a chunking job, a reranker and glue code between them. Each piece is another service to run, secure and keep in sync with your documents, and the reranker is often the slowest and most expensive step.
HotKV puts the pipeline in the engine that already serves your application. Define a pipeline, ingest documents, and search it. Chunking, document metadata and hybrid search that mixes vector similarity with BM25 keyword scoring all run server-side, and a rerank cache keeps cross-encoder scores so a repeated query and passage pair is never scored twice.
One chunk per paragraph. Use your embedding model's dimensions (3 keeps the example short).
RAG.CREATE faq 3 STRATEGY paragraphEach document is chunked server-side and stored with its metadata and one vector per chunk.
RAG.INGEST faq doc:1 "To reset your password, click Forgot password on the login screen.\n\nBilling questions go to the billing team." META source help-center VECTORS 0.9,0.1,0.0 0.0,0.2,0.9Vector similarity and keyword relevance in one query, restricted to one source.
RAG.SEARCH faq "how do I reset my password" K 2 ALPHA 0.5 VECTOR 0.88,0.12,0.01 FILTER source help-centerScores from the cross-encoder are cached per query and chunk, in a namespace made with RERANK.CREATE, so a popular query does not pay for reranking again.
RERANK.GET faq_scores "reset password|doc:1:0"The best chunks go to the model as context, so the answer comes from the help center instead of a guess. RAG.STATS shows what the pipeline holds.
RAG.STATS faqArticles and resolved tickets are ingested with their product and language as metadata. Each answer is grounded in the right product's documentation.
Contracts and policies are split by paragraph so retrieved passages are complete clauses, and keyword scoring catches exact terms such as clause numbers.
Runbooks, design documents and postmortems become searchable by meaning for an on-call assistant.
Fixed-size, sentence or paragraph chunking. Fixed-size chunks take a size and overlap you choose.
RAG.CREATEVector similarity and BM25 keyword scoring in one query, with ALPHA setting the balance.
RAG.SEARCHAttach key and value pairs at ingest and filter on them at search time.
RAG.INGESTFILTERKeep cross-encoder scores for query and passage pairs so repeats are free.
RERANK.GETRERANK.SETNo. You generate embeddings with the model you prefer and pass them with VECTORS when ingesting and VECTOR when searching.
Yes. RAG.SEARCH takes the query text for keyword scoring, and the VECTOR option adds vector similarity. ALPHA sets how the two scores are blended.
RAG pipelines and the rerank cache are part of the Performance and Scale plans.
HotKV speaks the Redis protocol, so you can point an existing client at it and run these same commands.