Skip to content
mif-rs

Stored vector blob does not match its dim column

Type URI: https://modeled-information-format.github.io/mif-rs/references/errors/vector-blob-mismatch/v1 HTTP status: 500 Exit code: 1 Emitted by: mif-store (StoreError::VectorBlobMismatch)

Message

Section titled “Message”
vector blob for '{id}' decoded to {actual_len} components, but the dim column says {expected_dim}

Cause

Section titled “Cause”

A row’s vector blob, decoded as little-endian f32 components, produced a different count than the row’s own dim column claims. Same threat model as corrupt-dimension/v1 — external tampering, a crash mid-write, or disk bit-rot — but the corruption lives in the vector blob rather than the dim column. get() and top_k_similar() both reject this rather than silently returning a truncated vector.

Suggested fix

Section titled “Suggested fix”

Unspecified — this indicates a corrupt or inaccessible database file. Verify the file’s permissions and integrity, or delete it to let mif-store recreate it.