Skip to content

[Store] Add Milvus #314

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 19, 2025
Merged

[Store] Add Milvus #314

merged 1 commit into from
Aug 19, 2025

Conversation

Guikingone
Copy link
Contributor

Q A
Bug fix? no
New feature? yes
Docs? yes
Issues None
License MIT

Hi 👋🏻

This PR aim to add the support for Milvus in the Store component, it also introduce a DroppableStoreInterface that allows to remove the current database (because it's boring to remove the volumes and drop the services from Docker 😄 ).

Thanks for the feedback.

@carsonbot carsonbot added Feature New feature Store Issues & PRs about the AI Store component Status: Needs Review labels Aug 14, 2025
@chr-hertel
Copy link
Member

Needs a rebase after #317

Copy link
Member

@chr-hertel chr-hertel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alright, I played a little bit around with it and also running Milvus on cloud.zilliz.com.

On thing, that made it harder for me is the database - this is not actually needed. With the cloud service i ran into 403, but worked when commenting it out - and also locally it works without creating the database first.

I think the database should at least be optional - maybe if database is not null or something?

@Guikingone
Copy link
Contributor Author

Ah yes, tested the cloud version and it comes with an existing database, hum, one solution might be to add a forceDatabaseCreation (name open to debate 😄 ) option in the initialize method, this way, if the option is set to true, we create the database, otherwise, we "expect" that it exist 🤔

@Guikingone
Copy link
Contributor Author

Small update here @chr-hertel @OskarStark, I removed the DroppableStoreInterface following the discussion in #285, it's better to do a "big" PR to updated than introducing something that will be removed for clarity later.

Copy link
Member

@chr-hertel chr-hertel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@Guikingone
Copy link
Contributor Author

I just rebased the branch against main, @OskarStark, I will work on renaming the env variable in a new PR 🙂

@chr-hertel
Copy link
Member

Thank you @Guikingone.

@chr-hertel chr-hertel merged commit 49013be into symfony:main Aug 19, 2025
8 checks passed
@Guikingone Guikingone deleted the store/milvus branch August 20, 2025 07:18
chr-hertel added a commit that referenced this pull request Aug 20, 2025
This PR was squashed before being merged into the main branch.

Discussion
----------

[Store] Add ManagedStoreInterface

| Q             | A
| ------------- | ---
| Bug fix?      | no
| New feature?  | yes
| Docs?         | yes
| Issues        | #285 #314
| License       | MIT

Hi 👋🏻

This PR aim to introduce the `ManagedStoreInterface` as discussed in #285, `Store` is a critical part of this library so I'm not gonna pretend that I know how each store currently work but here's the refactoring for most of them, tests must be improved but here's the first "draft".

This PR does not include the related commands.

Commits
-------

35aec00 [Store] Add ManagedStoreInterface
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature New feature Status: Reviewed Store Issues & PRs about the AI Store component
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants