Wildcard Queries (Converter issue)

Matias

Vote:

I go through bunch of pages like:
https://world.optimizely.com/forum/developer-forum/Commerce/Thread-Container/2021/6/ability-to-search-complex-object-with-contain-or-prefix-value-via-epi-server-find-query/
http://joelabrahamsson.com/wildcard-queries-with-episerver-find/
https://world.optimizely.com/blogs/drew-null/dates/2018/4/find-wildcardquery-and-best-bets---a-workaround/
https://world.optimizely.com/blogs/mark-stott/dates/2021/11/optimizely-search-wildcard-queries-and-best-bets/

tldr; the wildcard query should looks like `$"*{query}*"` but (I guess recently) there was a change introduced, and it start to throw:

(CMS 11 vs CMS 12)

so it throws on widldcards now :blowing-head:

If I remove logic adding '*' it won't perform "wildcard search"...

Change introduced in version 15.0.0. In version 14.2.4 there is no such check.

I patched it temporary by downgrading the version to 14.2.4, but I do not think it should be the way to do it :D

#311311

Edited, Oct 23, 2023 12:22

Quan Mai

Vote:

Yes the story is FIND-9992. I believe the reason was prefix wildcard is very expensive to perform which affects the cluster itself. So it's the new limitation we'll have to live with

#311386

Oct 24, 2023 6:14

Try our conversational search powered by Generative AI!

Wildcard Queries (Converter issue)