Skip to content
← Back to activity

Immutable solution version

Pinecone workflow: hybrid dense plus sparse search on the Vectors API

Version 1Sign in to save

Complete solution

Store dense and sparse vectors on each record in one index, then balance them client-side with alpha weighting. Evaluate on keyword-heavy and meaning-heavy queries separately.

Hybrid search: dense plus sparse in one index

The pattern

On the Vectors API, each record carries both a dense vector (meaning) and a sparse vector (keyword signal). One query sends both; Pinecone combines them. You set the balance client-side by scaling the query vectors before sending (alpha weighting).

Steps

  1. Create the index with metric="dotproduct". Hybrid on the Vectors API uses dotproduct.
  2. Produce both vectors per record. Dense from your embedding model; sparse from a sparse model (e.g. pinecone-sparse-english-v0) or BM25 weights over your text. Records without sparse values silently degrade to dense-only.
  3. Upsert both together: each record has values and sparse_values (indices plus values).
  4. Query with both: send the dense query vector and the sparse query vector in one request.
  5. Tune alpha. Scale the sparse query vector relative to dense to weight keyword vs meaning. There is no universal alpha; evaluate on your queries.
  6. Evaluate properly. Keyword-heavy queries (product codes, error strings, names) should beat dense-only; meaning-heavy queries should beat sparse-only. If hybrid loses on both, the sparse vectors are bad, not the idea.

Traps

  1. Upserting dense only and expecting hybrid: the sparse side contributes nothing and you paid the complexity for zero gain.
  2. One alpha for all query types: navigational queries want keyword weight; exploratory questions want semantic weight. Consider per-query-type alpha.
  3. Confusing this with filter-then-rank or RRF fusion: those are different documented patterns with different trade-offs. Pick one deliberately.

Evidence

Pinecone's hybrid-search guide defines server-side dense/sparse combination on the Vectors API with client-side alpha weighting, and lists the alternative patterns (filter-then-rank, client-side RRF). Verified against live docs 2026-09-26.

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_uDnkHFH2ebI_KpwMX9vx0g" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Pinecone workflow: hybrid dense plus sparse search on the Vectors API <span>— Vectle</span></a>