starred/minne
1
0
Fork 0
mirror of https://github.com/perstarkse/minne.git synced 2026-01-11 20:50:24 +01:00
Code Issues Packages Projects Releases 10 Wiki Activity

Incorrect vector dimension #2

New Issue
Closed
opened 2025-12-29 05:18:40 +01:00 by adam · 3 comments
adam commented 2025-12-29 05:18:40 +01:00
Owner
Copy Link

Originally created by @ard0gg on GitHub (Oct 10, 2025).

I'm having issue using a the nomic-embed-text model with ollama. I've updated the embedding dimensions to 768 per nomic documentation. However, whenever I try to ingest data I get this error

minne_app        | 2025-10-10T17:39:59.331187Z ERROR main: Worker process error: Ingestion Processing error: Database error: Incorrect vector dimension (768). Expected a vector of 1536 dimension.
Originally created by @ard0gg on GitHub (Oct 10, 2025). I'm having issue using a the nomic-embed-text model with ollama. I've updated the embedding dimensions to 768 per nomic [documentation](https://docs.nomic.ai/platform/embeddings-and-retrieval/text-embedding). However, whenever I try to ingest data I get this error ```bash minne_app | 2025-10-10T17:39:59.331187Z ERROR main: Worker process error: Ingestion Processing error: Database error: Incorrect vector dimension (768). Expected a vector of 1536 dimension. ```
adam closed this issue 2025-12-29 05:18:40 +01:00
adam commented 2025-12-29 05:18:40 +01:00
Author
Owner
Copy Link

@perstarkse commented on GitHub (Oct 10, 2025):

Thanks for reporting! The only current workaround would be to ingest content with the default embedding dimensions, and then switch. I’ll get to fixing this at the end of the weekend!

@perstarkse commented on GitHub (Oct 10, 2025): Thanks for reporting! The only current workaround would be to ingest content with the default embedding dimensions, and then switch. I’ll get to fixing this at the end of the weekend!
adam commented 2025-12-29 05:18:40 +01:00
Author
Owner
Copy Link

@perstarkse commented on GitHub (Oct 12, 2025):

I've now implemented a fix in commit b7344644dc, and it should be in the latest release

@perstarkse commented on GitHub (Oct 12, 2025): I've now implemented a fix in commit b7344644dc2daa3c4ab5eb680e8a626ee4dfc526, and it should be in the latest release
adam commented 2025-12-29 05:18:41 +01:00
Author
Owner
Copy Link

@ard0gg commented on GitHub (Oct 12, 2025):

Thanks for the quick fix!

@ard0gg commented on GitHub (Oct 12, 2025): Thanks for the quick fix!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/minne#2
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?