Re: Partial / starts with searching

2009-02-13 Thread d-fader
o get some benefit from CachingWrapperFilter. And ignore my entire diatribe about whether you can restrict your wildcards to 3 or more characters, that approach doesn't fit your problem space at all Best Erick On Fri, Feb 13, 2009 at 8:39 AM, d-fader wrote: Well, it worked. I indexed

Re: Partial / starts with searching

2009-02-13 Thread d-fader
his topic, see the following for that discussion: http://www.lucidimagination.com/search/document/65a13a1dbd7035ae/i_just_don_t_get_wildcards_at_all#65a13a1dbd7035ae Best Erick On Fri, Feb 13, 2009 at 3:05 AM, d-fader wrote: Hi, I've actually posted this message in de dev mailing list earlier, because I though my

Re: Partial / starts with searching

2009-02-13 Thread d-fader
alysis/ngram/EdgeNGramTokenFilter.html The classes are available in the contrib/analyzer module. You might want to boost edges a bit more than inner parts, start trying out with something like 3-5 grams. Be aware, this will produce a rather large index. karl 13 feb 2009 kl. 10.43 skr

Re: Partial / starts with searching

2009-02-13 Thread d-fader
;t understand how Google manages to do this :) Jori. Karl Wettin wrote: Hi again Jori, did you try N-grams as suggested in the reply on -dev? karl 13 feb 2009 kl. 09.05 skrev d-fader: Hi, I've actually posted this message in de dev mailing list earlier, because I though my &#x

Partial / starts with searching

2009-02-13 Thread d-fader
Hi, I've actually posted this message in de dev mailing list earlier, because I though my 'issue' is a limitation of the functionality of Lucene, but they redirected me to this mailinglist, so I hope one of you guys can help me out :) Maybe the 'issue' I'm addressing now is discussed thouroughly