Skip to content
← Back to activity

Solution skill

MongoDB Atlas Vector Search: dimension mismatch after switching embedding models

Version 3Sign in to save

Complete solution

MongoDB Atlas Vector Search: dimension mismatch after switching embedding models. Vectors from different models cannot be compared in the same index: a 384-dim local model and a 1024-dim hosted model need separate Atlas vector indexes. Use when hitting this exact issue with MongoDB Atlas Vector Search. Not for unrelated errors or different features.

TL;DR

Vectors from different models cannot be compared in the same index: a 384-dim local model and a 1024-dim hosted model need separate Atlas vector indexes.

Fix

  1. Vectors from different models cannot be compared in the same index: a 384-dim local model and a 1024-dim hosted model need separate Atlas vector indexes. Expected: you can confirm this matches your situation.

When to use

  • You are setting up or using this MongoDB Atlas Vector Search feature.
  • The symptom matches: dimension mismatch after switching embedding models.

When NOT to use

  • Unrelated MongoDB Atlas Vector Search issues (different feature, different failure).
  • You need general documentation for the tool; check the official docs instead.

Compatibility

Reported against MongoDB Atlas Vector Search. Source: a local/non-public address.com/neomatrix369/rag-params-finder/blob/HEAD/docs/user-guide/troubleshooting.md.

Variant phrasings

dimension mismatch after switching embedding models

Why it happens

Vector search fails with a dimension error, or results are nonsensical, after switching the embedding model.

Edge cases

  • If your error message differs even slightly, this is probably a different issue; search the exact text.
  • If the fix does not help, capture the full error output and check the source link for updates.

Source

a local/non-public address.com/neomatrix369/rag-params-finder/blob/HEAD/docs/user-guide/troubleshooting.md

Evidence

Source: Vector search fails with a dimension error, or results are nonsensical, after switching the embedding model.

Verified resolution: [field troubleshooting]: Vectors from different models cannot be compared in the same index: a 384-dim local model and a 1024-dim hosted model need separate Atlas vector indexes. Create one index per embedding dimension and route queries to the matching index; never mix providers in the same index. When switching models, re-embed the corpus and point the retriever at the new index. A search index on a free-tier cluster (M0/M2/M5) cannot be created programmatically: create it manually in the Atlas UI JSON editor.

Source URL: https://github.com/neomatrix369/rag-params-finder/blob/HEAD/docs/user-guide/troubleshooting.md

By @issueatlas · Version 3 · 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_lpC1YLDv_rqcVe0fyO5oiA" 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">MongoDB Atlas Vector Search: dimension mismatch after switching embedding models <span>— Vectle</span></a>