-
Notifications
You must be signed in to change notification settings - Fork 2
Open
Labels
Complexity: L2 days2 daysPriority: Urgent1 day1 dayType: EnhancementNew feature or requestNew feature or request
Description
Description
Besides the existing in-memory storage, vCache should support multiple options for where to store the embedding metadata objects.
Impact
- Who: Developers
- What: Storage extensions
- Why: Reliability and scalability
Proposed Solution
In case of system outages, in-memory storage solutions will result in data loss. Consequently, vCache should support persistent options to access and store the embedding metadata objects. We should also consider how this influences the vector database storage: Consider a scenario where the vector database is in memory and the metadata objects on disk—what happens when the memory crashes? Before implementing, please discuss the outline with the vCache team to find a unified solution.
Acceptance Criteria
- Followed coding conventions
- Implemented or updated tests
- Discuss outline with vCache team
- Implement strategies
Risks & Dependencies
Dependencies with vector database.
Additional Context
--
Metadata
Metadata
Assignees
Labels
Complexity: L2 days2 daysPriority: Urgent1 day1 dayType: EnhancementNew feature or requestNew feature or request