high severityChromaDB get() method
When using `collection.get(include=['embeddings', 'metadatas'], where={...})` or non-existent `ids` with a non-matching metadata filter, `ids` and `metadatas` return empty lists, but `embeddings` returns *all* embeddings in the collection (e.g., 153MB for 4000 docs). Causes high memory usage, slowness, and incorrect results.
Root cause
Bug in the metadata join logic during `get()` queries with `where` filters that match no entries, causing all embeddings to be returned despite empty `ids` and `metadatas`. Primarily affected server/REST API mode.
ChromaDBmetadata filteringwhere clauseget queryembeddings leakserver mode