*Summary:*
Lucene indexes appear to revert to some past state after an application
restart.
*Background:*
We're running an enterprise application written in Java/Spring/Hibernate,
deployed within Jetty, with a Postgres backend. See below for version info.
We use Lucene to index certain componen
Hi,
> So the "usual" answer is either to use the KeywordRepeatFilterFactory, or
> use a copyField that doesn't stem and when exact matches are required,
> search on that field.
Or even better search on both fields (stemmed and unstemmed, I generally also
have a ASCII-folded one) with SHOULD. An
It's actually a real pain to do this right considering all the different
analysis chains. As Modassar says, the KeywordRepeatFilterFactory
is often "good enough". It'll boost the exact match, but it won't actually
guarantee that only exact-match docs are returned.
Ideally, you'd want the option to
Can
anyone tell me why this option is not provided for Stemming.
I am not sure about it but the original token can be preserved by using
too.
To avoid any duplicate token in the document can be used at the end of
analysis chain.
Hope this helps.
Regards,
Modassar
On Tue, Aug 25, 2015 at 2:12
Hi,
I was working with Lucene 5.2 and trying to index some document. I am using
EnglishMinimalStemFilterFactory and I found that there is no option for
keeping the original text as wel as analyzed term into lucene index.
WordDelimiterFilterFactory provides preserveOriginal option to do this. Can
