Strixa AI
TopicsSearchPricing
Sign inStart tracking

Signal Detail

Loading signal detail

Reading this signal card's judgment, risks, and evidence.

Strixa AI
TopicsSearchPricing
Sign inStart tracking
Back to Signal Feed
CodeTracked since May 18, 2026

Fix memsearch to load Milvus collections before search

A reported issue in memsearch showed that after indexing, `memsearch search` can fail with `MilvusException` 101 (`Collection 'memsearch_chunks' is in state 'released'`) on newer `pymilvus`/`milvus-lite` versions because `_ensure_collection` in `memsearch/store.py` never loads the collection after attach/create. The proposed fix is to call `client.load_collection(collection_name)` in both collection branches (`has_collection` and create path), restoring normal hybrid search behavior on current client versions.

memsearchpymilvusmilvus-liteMilvusException

Signal Intelligence

Confidence Level94%
Worth Continued TrackingFinal score 82% with 1 evidence item.
Primary Impact Areas
memsearchpymilvusmilvus-lite

What Happened

  • A reported issue in memsearch showed that after indexing, `memsearch search` can fail with `MilvusException` 101 (`Collection 'memsearch_chunks' is in state 'released'`) on newer `pymilvus`/`milvus-lite` versions because `_ensure_collection` in `memsearch/store.py` never loads the collection after attach/create. The proposed fix is to call `client.load_collection(collection_name)` in both collection branches (`has_collection` and create path), restoring normal hybrid search behavior on current client versions.
  • A reported issue in memsearch showed that after indexing, `memsearch search` can fail with `MilvusException` 101 (`Collection 'memsearch_chunks' is in state 'released'`) on newer `pymilvus`/`milvus-lite` versions because `_ensure_collection` in `memsearch/store.py` never loads the collection after attach/create. The proposed fix is to call `client.load_collection(collection_name)` in both collection branches (`has_collection` and create path), restoring normal hybrid search behavior on current client versions.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Adds an explicit collection-load step inside `memsearch/store.py`’s `_ensure_collection` for both existing and newly created collections, ensuring search is only invoked after collection state is loaded and preventing the `released`-state rejection introduced by newer Milvus clients.

Why Track This

Why It Matters

Users running memsearch indexing pipelines on modern `pymilvus`/`milvus-lite` installations can resume `search` immediately after indexing without random hard failures, which removes a production break where retrieval operations stopped working and required manual dependency workarounds. This happens because newer client versions no longer auto-load collections, so the fix aligns memsearch with explicit load requirements; teams should keep watching for environments where `load_collection` intermittently fails because the patch handles load errors with a broad `try/except`, which could mask retry-worthy root causes.

Impact

Users running memsearch indexing pipelines on modern `pymilvus`/`milvus-lite` installations can resume `search` immediately after indexing without random hard failures, which removes a production break where retrieval operations stopped working and required manual dependency workarounds. This happens because newer client versions no longer auto-load collections, so the fix aligns memsearch with explicit load requirements; teams should keep watching for environments where `load_collection` intermittently fails because the patch handles load errors with a broad `try/except`, which could mask retry-worthy root causes.

What To Watch Next

  • Watch whether memsearch becomes a repeated pattern.
  • Track follow-up changes around AI Coding Agents.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: load_collection_errors_masked_by_broad_exception_handling, client_version_specific_behavior_change.
Open Topic TimelineOpen Technical EventOpen Original Sourceload_collection_errors_masked_by_broad_exception_handling / client_version_specific_behavior_change / post_load_search_state_regression_on_older_clients

Supporting Evidence

GITHUB ISSUEHigh Trust

zilliztech/memsearch Issue #542: search fails with "released" state — Collection released after _ensure_collection on memsearch 0.4.2 / pymilvus 3.0 / milvus-lite 3.0

The indexed corpus exists, but search fails with `Collection ... is in state 'released'; call load() before search/get/query`, because newer clients require an explicit collection load.