Contrib.social

Unable to create a Milvus search API server on Zilliz Cloud

Open on Drupal.org →
Created on 15 September 2024, 5 days ago
Updated 19 September 2024, 1 day ago

Problem/Motivation

When trying to add a Search Api Server using a Milvus DB hosted on Zilliz, the site returns an error:

Exception: Failed to create collection in Drupal\vdb_provider_milvus\Plugin\VdbProvider\MilvusProvider->createCollection() (line 187 of modules/contrib/ai/modules/vdb_providers/vdb_provider_milvus/src/Plugin/VdbProvider/MilvusProvider.php).

However, on the Zilliz dashboard, the cluster is clearly created. But in Search API, the server is not. If I try to submit the form again with the created collection name, I get the error

"The collection already exists in the selected vector database."

Seems like a bug!

Steps to reproduce

I have a drupal 10.3.5 site hosted locally with a standard ddev setup, AI module, AI Search, Search API, and Keys modules installed. The collection does get created on Zilliz so no problems with the keys or connection.

I go to admin/config/search/search-api and choose "+ Add server". I don't think the settings matter but I choose these options:

Server name: Milvus Search
Vector DB: Milvus DB
Tokenizer chat model: OpenAI - gpt-3.5-turbo
Database Name: default
Collection: tryingout
Similarity Metric: Cosine Similarity
Embeddings Strategy: Metadata enriched chunks
Maximum chunk size: 500
Minimu chunk overlap: 100
Metadata maximum percentage: 30%
Embeddings Engine: OpenAI | text-embedding-3-small
Dimensions: 1536

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report
Status

Closed: won't fix

Version

1.0

Component

AI Search

Created by

benthv

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @benthv
  • Comment 5 days ago →
    benthv
  • Comment 5 days ago →
    🇩🇪Germany Marcus_Johansson

    This is a know and fixed bug - since we released Alpha6 Zilliz Cloud has added rate limiting and because the AI Search checks if the collection exists, before it creates it, the rate limiter messages is given back. Unfortunately the Zilliz Cloud rate limiter still runs the task.

    In the 1.0.x-dev we have a first version that works better. There might come an actual queue system later if you use Zilliz Cloud, but the 1.0.x-alpha6 version still has this problem.

    What you can do now is:
    * Wait for 1.0.x-alpha7
    * Use the 1.0.x-dev
    * Write a patch for 1.0.x-alpha6

    I will close this issue, since its known. Feel free to close the issue it if you don't want to write a patch or wait for someone to do it

  • Status changed to Closed: won't fix 1 day ago
  • Comment 1 day ago →
    🇩🇪Germany Marcus_Johansson

    Alpha7 is released and should fix this issue. Please make sure to kill of collections in Zilliz if you have free account, since they only allow for 2.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024