Pinecone hybrid search relevance mismatch after processing 10k batch queries

brown pinecones

Pinecone Hybrid Search Relevance Mismatch After Processing 10k Batch Queries Problem In a production recommendation pipeline we issue batches of up to 10 000 hybrid search requests to a Pinecone index. Each request supplies a dense embedding vector and a metadata filter (e.g., category = ‘sports’). The first few thousand queries return results ordered by the … Read more

vLLM RAG hybrid search weight imbalance on edge node after config change

A man with styled hair wearing a white t-shirt with red lettering

Problem After a recent configuration change on an edge‑computing node running vLLM, the Retrieval‑Augmented Generation (RAG) hybrid search started to favor one modality almost exclusively. In practice: Keyword‑based retrieval (bm25) returns no results even when the query contains exact terms. Dense vector retrieval dominates the relevance score, causing unrelated passages to be selected. Latency spikes … Read more

Hybrid search score mismatch after dense model update in CI

A close up of a cell phone with a keyboard

Problem Description Nightly integration tests for the DeepSeek search service started failing after the dense encoder was upgraded to v2.1. The regression suite validates that the top‑k ranking produced by the hybrid (dense + sparse) scorer is deterministic across builds. After the model update the following error appeared in the CI logs: HybridScoreMismatchError: dense_score=0.8423, sparse_score=0.2311, combined_score variance … Read more

ONNX Runtime hybrid search scoring inconsistencies on GPU

img IX mining rig inside white and gray room

Problem – HybridSearch Scoring Inconsistencies on GPU In a development sandbox (Ubuntu 22.04, NVIDIA A10G, ONNX Runtime 1.18, PyTorch backend) a BERT‑based reranker that uses the HybridSearch operator returns different top‑k results when the model is executed on the CPU (FP32) versus the GPU (FP16 mixed‑precision). Typical symptoms include: Top‑5 candidate order differs by up to three positions. … Read more

Mistral AI hybrid search scoring discrepancy between staging and production

a person holding a cell phone in their hand

Problem Description Symptoms and Impact After the nightly CI/CD pipeline retrains the Mistral AI embedding model and rolls out the new container image, the /v1/hybrid-search endpoint returns noticeably different relevance scores in the production Kubernetes cluster compared to the staging cluster. Typical observations: Top‑K results differ in ordering despite identical query text. Score drift of … Read more

Gemini hybrid search scoring inconsistency in air-gapped environment

a close up of a cell phone with buttons

Problem – Gemini Hybrid Search Scoring Inconsistency in an Air‑Gapped Deployment Engineers deploying Google Gemini in a hybrid search configuration (vector + keyword) inside an air‑gapped environment have reported that the relevance scores returned for the same query differ dramatically between the local vector database and the remote knowledge‑base (KB) component. Typical manifestations include: Score … Read more