llamaIndex - 💡(How to fix) Fix [Question]: How large data set can be reingested to milvus and query it using llamaindex when I need to change the embedding model to a new one? [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
run-llama/llama_index#20848Fetched 2026-04-08 00:30:40
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
commented ×1labeled ×1mentioned ×1subscribed ×1
RAW_BUFFERClick to expand / collapse

Question Validation

  • I have searched both the documentation and discord for an answer.

Question

I have milvus collections for each tenant which have thousands of entities. Now I need to change the embedding model to another one, which is not retrieving the information related to the old indices. How to handle this?

extent analysis

Fix: Rebuild Indices for New Embedding Model

Rebuilding indices for the new embedding model will allow Milvus to retrieve information related to the old indices.

Step-by-Step Solution Plan:

1. Drop Old Indices

DROP INDEX <old_index_name> ON <collection_name>;

Replace <old_index_name> and <collection_name> with the actual names of your index and collection.

2. Rebuild Indices for New Embedding Model

CREATE INDEX <new_index_name> ON <collection_name> USING IVF_FLAT (embedding);

Replace <new_index_name> and <collection_name> with the actual names of your new index and collection.

3. Rebuild the Vector Table

ALTER TABLE <collection_name> REBUILD;

Replace <collection_name> with the actual name of your collection.

4. Rebuild the Index for the Vector Table

REBUILD INDEX <new_index_name> ON <collection_name>;

Replace <new_index_name> and <collection_name> with the actual names of your new index and collection.

Verification

  • Check if the new embedding model is being used correctly by querying the collection.
  • Verify that the information related to the old indices is being retrieved correctly.

Extra Tips

  • Make sure to back up your data before rebuilding indices.
  • Rebuilding indices can be a time-consuming process, so plan accordingly.
  • Consider using a more efficient indexing strategy for your use case.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING