- Issue created by @Vivek Panicker
- 🇬🇧United Kingdom scott_euser
I don't think we should do this in AI module; we rely on the generation of the vector during search matching exactly the process used to generate the vectors during indexing.
Would be open to an Event developers can subscribe to allowing $params in SearchApiAiSearchBackend::search() to be modified (in which case they can (at own risk) provide $params['vector_input'] (since we check if that's empty first already before generating).
- Merge request !292Issue #3489566: Allowed to do vector search by user supplied vector. → (Open) created by Vivek Panicker
- 🇮🇳India Vivek Panicker Kolkata
Hey @scott.
The code change I have pushed takes the vector input param from the query option.
So we can add it to the query during query alter phaese or while writing the vector services provider. - 🇬🇧United Kingdom scott_euser
That makes sense! I'll try to get to manual testing this week.
- 🇮🇳India Vivek Panicker Kolkata
Thank you!
I myself have not tested it thouroughly.
Will update if I face any issues because of this change. - 🇬🇧United Kingdom scott_euser
Suggesting a slight refactor here as the code is getting a lot of nested ifs which makes it harder to follow + we have some inefficiency since we load embedding engine yet don't need to in your new case where we have an embedding already
Thanks!
- Status changed to Needs work
19 days ago 12:00pm 10 July 2025 - 🇩🇪Germany marcus_johansson
@scott_euser - since there has been no answer here, do you still feel like this is something to keep? I've upped it to 1.2.0 target.
- 🇬🇧United Kingdom scott_euser
Personally I do not have any need for it, I cannot remember who/where this got raised - perhaps we postpone and they can chime in if its still required.