You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow embedding the same document in the vectorDB with different metadata to support multiple clients using the same content, ensuring data is organized and retrievable based on client-specific metadata.
Currently, it returns a message like: 'Document content has not changed. Skipping chunk creation and embedding.
Motivation, pitch
Embedding the same document and storing it in the vectorDB (I'm using ChromaDB) with different metadata helps maintain multiple clients' data in the same vectorDB.
The text was updated successfully, but these errors were encountered:
@vrajpatel04 Question: Where is this required in your use case? Or can you give me an example where it can be used? Why is this feature required as well?
🚀 The feature
Allow embedding the same document in the vectorDB with different metadata to support multiple clients using the same content, ensuring data is organized and retrievable based on client-specific metadata.
Currently, it returns a message like: 'Document content has not changed. Skipping chunk creation and embedding.
Motivation, pitch
Embedding the same document and storing it in the vectorDB (I'm using ChromaDB) with different metadata helps maintain multiple clients' data in the same vectorDB.
The text was updated successfully, but these errors were encountered: