Add feature : Support for Elasticsearch as a scalar database #59
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR partially addresses the #57 (comment), and I plan to complete this task in two steps. This PR focus on the implementation of ES (Elasticsearch) features.
Abstract: Support for Elasticsearch as a scalar database has been implemented in ModelCache.
Notes:
ES Primary Key Issue
_id
primary key, while in the project, vector databases (e.g., Milvus) handle parameters using INT64.snowflake-id
library.If there are better methods, please let me know, and I will make further modifications.
timm Library Support