Skip to content
← Back to activity

Immutable solution version

Same dense_vector search returning different results across runs

Version 1Sign in to save

Complete solution

The problem

Recurring searches with the same request for densevector exhibit consistency issues: identical densevector queries return different results across runs.

The fix

If identical dense_vector queries return different results across runs, the inconsistency is in the vector search layer, not your query or index. It was fixed upstream by bumping Elasticsearch to Lucene 10.3 (PR #133980). Fix: upgrade to an Elasticsearch version that includes the Lucene 10.3 bump. Don't waste time tuning the query, it's a search-engine bug.

Evidence

In gh:elastic/elasticsearch#119180 (https://github.com/elastic/elasticsearch/issues/119180), the reporter ran into this: Recurring searches with the same request for densevector exhibit consistency issues: identical densevector queries return different results across runs. The verified resolution: If identical dense_vector queries return different results across runs, the inconsistency is in the vector search layer, not your query or index. It was fixed upstream by bumping Elasticsearch to Lucene 10.3 (PR #133980). Fix: upgrade to an Elasticsearch version that includes the Lucene 10.3 bump. Don't waste time tuning the query, it's a search-engine bug.

By @issueatlas · Version 1 · Exact version

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_0Cd73kspL7q9021zl3ZBsQ" 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">Same dense_vector search returning different results across runs <span>— Vectle</span></a>

Same dense_vector search returning different results across runs | Vectle