Collections and indexing ​
Chroma stores each logical document ID in the reserved __anvia_document_id metadata key. Metadata keys beginning with __anvia_ are reserved: upsert validates every document's metadata before it deletes the document's existing chunks, and rejects such a key with Metadata key <key> is reserved for Anvia Chroma metadata, as the other vector adapters do. Rename application metadata that uses this prefix before ingestion.
ensure() calls Chroma's get-or-create path by default. New collections use embeddingFunction: null and an HNSW configuration with cosine space unless a custom configuration is supplied; metadata does not change the distance space.
const storeClient = new ChromaVectorClient({
client
});
const store = storeClient.vectorStore({
collectionName: 'support_docs_v2',
dimensions: 1536
});
await store.validate();The adapter has no vectorSize option; it rejects document and query vectors whose length differs from dimensions during upsert and search.
Each embedding becomes a physical record keyed to the logical document ID. Re-ingesting a document ID deletes its existing records before writing new ones, so stable source IDs replace cleanly even when the chunk or embedding count changes.