.ch]
> Sent: Friday, December 07, 2012 10:16 AM
> To: java-user@lucene.apache.org
> Subject: Alternative for WildcardQuery with leading *
>
> In order to provide suggestions our query also includes a
> "WildcardQuery with a leading *", which, of course, has a HUGE
>
10:16 AM
> To: java-user@lucene.apache.org
> Subject: Alternative for WildcardQuery with leading *
>
> In order to provide suggestions our query also includes a "WildcardQuery
> with a leading *", which, of course, has a HUGE performance impact :-(
>
> E.g.
> Say we
cht-
Von: Shai Erera [mailto:ser...@gmail.com]
Gesendet: Freitag, 7. Dezember 2012 10:20
An: java-user@lucene.apache.org
Betreff: Re: Alternative for WildcardQuery with leading *
Really off the top of my head, if that's an expected query, you can try to
index the words backwards (in that fiel
Really off the top of my head, if that's an expected query, you can try to
index the words backwards (in that field) and then convert the query *plan
to nalp* :).
You can also index the suffixes of words, e.g. vacancyplan, acancyplan,
cancyplan and so forth, and then convert the query *plan to pla
In order to provide suggestions our query also includes a "WildcardQuery with a
leading *", which, of course, has a HUGE performance impact :-(
E.g.
Say we have indexed "vacancyplan", then if a user typed "plan" he should also
be offered "vacancyplan" ...
How can this feature be implemented wit
