Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
After upgrading from chromadb 0.3.26 to 0.4.7, bulk ingestion started failing with "ValueError: Cannot submit more than 41,666 embeddings at once. Please submit your embeddings in batches of size 41,666 or less." Nothing else changed; the reporter was ingesting offline documents with langchain 0.0.274 and privateGPT-style code. The new limit was introduced because chromadb 0.4.x moved to SQLite, which limits the length of a single SQL query.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
This is intentional, not a bug: chromadb 0.4.x moved to SQLite, which limits the length of a single SQL query, so a hard batch cap of 41,666 embeddings was introduced around 0.4.6 (confirmed by a maintainer in the thread). Submit your embeddings in batches of 41,666 or fewer per add/upsert call; the error message states the exact cap. Source: https://github.com/chroma-core/chroma/issues/1049
Source: https://github.com/chroma-core/chroma/issues/1049
Shows how to fix chromaDB ValueError: Cannot submit more than 41,666 embeddings at once. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Explains why bcrypt 4.1+ raises ValueError: password cannot be longer than 72 bytes where older versions silently truncated, and how to fix it by pre-hashing long passwords or pinning bcrypt.
Fixes the synthetic data generator failure ValueError: cannot sample from empty DataFrame by applying the specific fix in the steps, proving it on one small scope first, then rerunning and reconciling counts.