Feature Request: Fallback options for remote embedding services about typesense HOT 2 OPEN

If you set up embedding, then you expect that it will always be filled.

• if you simply skip this stage, the embedding will never be filled in at all
• if you use a different model, there will be embedding from a different model that does not match the one used for requests

from typesense.

If you set up embedding, then you expect that it will always be filled.

• if you simply skip this stage, the embedding will never be filled in at all

Yes, if the embedding is unavailable at search time, it could be an option to fall back to using the other fields in the search, i.e. keyword search fields.

• if you use a different model, there will be embedding from a different model that does not match the one used for requests

What I had in mind was to have fallback embeddings indexed along with the main embeddings, if you want to have a fallback available. It is already possible to have multiple embedding fields and models at the same time, I believe, but if any model is unavailable the search fails.

from typesense.