It was a bit tricky to set up a Milvus collection for the first time. As it's possible to upload a collection JSON through the Milvus UI it makes sense to provide that collection with the module.

Issue fork ai_vdb_provider_milvus-3565173

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

nnevill created an issue. See original summary.

nnevill opened merge request !31

nnevill’s picture

nnevill
Primary language Ukrainian
Location Lutsk
commented
Status: Active » Needs review
nnevill’s picture

nnevill
Primary language Ukrainian
Location Lutsk
commented
Assigned: nnevill » Unassigned
scott_euser’s picture

scott_euser commented
Category: Support request » Bug report
Status: Needs review » Needs work

Hmmmm I think programmatically we are attempting to create the collection here https://git.drupalcode.org/project/ai_vdb_provider_milvus/-/blob/2.0.x/s... on resave of the provider. It seems like we probably need to trigger that code elsewhere too?

E.g. on server status page, flag collection not ready, and have a link like 'Automatically create collection now' which then triggers that same code. I suppose roughly similar to how solr deals with it, letting you solve via Drupal UI when collection is missing.

I think steps to reproduce are essentially something like:

  1. Developer 1 sets up milvus locally and pushes config export to repo
  2. Developer 2 pulls down and does ddev start
  3. Because Developer 2 did not use the UI, the above code is never triggered for them, so Collection doesn't exist in their ddev

Let me know what you think of the above