mirror of
https://github.com/Mintplex-Labs/anything-llm.git
synced 2026-03-02 22:57:05 -05:00
[BUG]: addDocumentToNamespace LanceDBError: Append with different schema #609
Labels
No labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
question
stage: specifications
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/anything-llm#609
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @majestichou on GitHub (Mar 28, 2024).
How are you running AnythingLLM?
Docker (local)
What happened?
I use the
sfr-embedding-mistral:q4_k_membedding model andLanceDB. I uploaded a document to the workspace and clicked the "Save and Embed" button. The error occurred.[OllamaEmbedder] Embedding 2 chunks of text with sfr-embedding-mistral:q4_k_m.
Inserting vectorized chunks into LanceDB collection.
As far as I know, the output of the sfr-embedding-mistral:q4_k_m model has dimension 4096, which cannot be changed. Can the data storage dimension of the LanceDB database be changed?
Maybe changing the data storage dimension from 384 to 4096 will fix this?
Are there known steps to reproduce?
No response
@timothycarambat commented on GitHub (Mar 28, 2024):
You cannot create a workspace and embed documents with one embedder, unembed all documents, swap embedders, and re-embed into that same workspace. The lanceDB schema is not removed when the last document is un-embedded (maybe it should to prevent this issues).
Just make a new workspace and it will work 👍
Default embedder is 384, so that is likely what happened here
@majestichou commented on GitHub (Mar 28, 2024):
YES!Just make a new workspace and it will work 👍 Thanks a lot! You did a great job!