Create a script or function to re-index existing data while switching/updating to a new model

[tacohiddink]

When switching to a different t2v-transformers model, do I have to re-index the current data that is already in Weaviate? Or does weaviate replace the vectors automatically? I am wondering what happens or what to do with existing data (that probably has vectors based on the old model)

I would consider it a valid use-case as models get better over time and one would probably switch to a newer model then. Probably need to re-index the whole db from scratch then.

Can a command be created to facilitate such a usse-case?

[zoltan-fedor]

I was thinking about the same.

I could imagine a similar process as to what you have when you do key rotation in a key-based authentication.

Basically having two embeddings, where the second one is the one currently built and once the build is complete, then you switch from the first to the second one.

[stale]

Thank you for your contribution to Weaviate. This issue has not received any activity in a while and has therefore been marked as stale. Stale issues will eventually be autoclosed. This does not mean that we are ruling out to work on this issue, but it most likely has not been prioritized high enough in the last months.
If you believe that this issue should remain open, please leave a short reply. This lets us know that the issue is not abandoned and acts as a reminder for our team to consider prioritizing this again.
Please also consider if you can make a contribution to help with the solution of this issue. If you are willing to contribute, but don't know where to start, please leave a quick message and we'll try to help you.
Thank you, The Weaviate Team