t; still get the undesirable results.
>>
>> Any idea why I am seeing this behaviour? Again, if I remove the
>> PorterStemFilter from my custom analyzer (which I use at both indexing and
>> search time) then I get the results I want (albeit I lose the other
>> functio
rStemFilter from my custom analyzer (which I use at both indexing and
> search time) then I get the results I want (albeit I lose the other
> functionality which I also need).
I hope that's a bit clearer. Any ideas to explain and/or resolve this?
Thanks,
-s
> functionality which I also need).
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/PorterStemFilter-causes-wildcard-searches-to-not-work-tp3525790p3544411.html
> Sent from the Lucene - Java Users mailing list archive at Nabble.com.
--
sage in context:
http://lucene.472066.n3.nabble.com/PorterStemFilter-causes-wildcard-searches-to-not-work-tp3525790p3544411.html
Sent from the Lucene - Java Users mailing list archive at Nabble.com.
t;
> Thanks,
>
> -sbs
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/PorterStemFilter-causes-wildcard-searches-to-not-work-tp3525790p3525790.html
> Sent from the Lucene - Java Users mailing list archive at Nabble.com.
>
> -
3.2.
Thanks,
-sbs
--
View this message in context:
http://lucene.472066.n3.nabble.com/PorterStemFilter-causes-wildcard-searches-to-not-work-tp3525790p3525790.html
Sent from the Lucene - Java Users mailing list archive at Nabble.com.
