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
In some situations, developers don't know how long the embedding collections need to persist in the database and would use ChromaDB as a cache. Manually deleting collections when the memory fills up becomes cumbersome and error-prone.
Describe the proposed solution
I would like to see the implementation of a time-to-live feature or a data eviction strategy within ChromaDB. This would automatically remove collections based on specified criteria, such as their age or a predefined expiration time.
Alternatives considered
Other solutions could involve periodically removing old data or implementing manual data pruning logic. However, these alternatives are less efficient and incur more overhead.
Importance
would make my life easier
Additional Information
No response
The text was updated successfully, but these errors were encountered:
Describe the problem
In some situations, developers don't know how long the embedding collections need to persist in the database and would use ChromaDB as a cache. Manually deleting collections when the memory fills up becomes cumbersome and error-prone.
Describe the proposed solution
I would like to see the implementation of a time-to-live feature or a data eviction strategy within ChromaDB. This would automatically remove collections based on specified criteria, such as their age or a predefined expiration time.
Alternatives considered
Other solutions could involve periodically removing old data or implementing manual data pruning logic. However, these alternatives are less efficient and incur more overhead.
Importance
would make my life easier
Additional Information
No response
The text was updated successfully, but these errors were encountered: