Re: Improving partial lookup results
Peter Bowyer <[email protected]>
| Newsgroups | gmane.comp.search.xapian.general |
|---|---|
| Message-ID | <CAJvSBVOU7cgZE4tDtmVVDc6VLs0OUaWa_3mBUutZXmQbJNQhgw@mail.gmail.com> |
Hi Olly, On Wed, 18 Sep 2019 at 22:09, Olly Betts <[email protected]> wrote: > If you really wanted to wildcard expand all words in a query string, > you'd have to parse it yourself, turn each word into an OP_WILDCARD > query and combine those. > Now you say it, that makes total sense (and seems so obvious). Testing, it matches as I want it to for "p bow". > I'd think that's likely to create a lot of false matches though, and > wildcards are relatively expensive so you might want to limit how many > words get wildcarded in a single query to avoid problems. > I was aiming to work round the false matches by also doing an exact match of the word(s) with a higher ranking factor. So if what's being wildcarded has an exact match also, it ranks higher. > There's expanded support for wildcards on git master, so you could > create an OP_WILDCARD query for `*ann*`, though that seems even more > likely to result in a lot of false matches and will tend to be more > expensive too. > Yes, I'm discarding this idea. Others are more important. Best, Peter -- Maple Design Ltd http://www.mapledesign.co.uk +44 (0)330 122 0034 Reg. in England no. 05920531 Prices exclude VAT where applicable