I was just going through compiling our sources against 4.0 and it seems there
are quite some API changes. Any major functionality changes from 2.4 - 4.0?
with respect to indexing/searching.
Thanks,
Sai.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Upgrade-Lucene-to-lates
QueryParser has a setAllowLeadingWildcard() method. Could that be relevant?
What version of lucene? Can you post some simple examples of what
does/doesn't work? Post the smallest possible, but complete, code that
demonstrates the problem?
With any question that mentions a custom version of som
forceMergeDeletes will only merge down segments with more than X%
deletions (X = 10% by default with TieredMergePolicy) ... so depending
on how many deletes you have it may or may not merge down to 5
segments like forceMerge(5) would.
Mike McCandless
http://blog.mikemccandless.com
On Fri, Jan
hi, I have an index where I add and delete a lot numerous documents that
are a few kb in size.
to keep space on disk stable, I have been doing forceMergeDeletes then
forceMerge(5) regularly (after I do a big clean during the night).
I am wondering if forceMergeDeletes would be sufficient for tha
This page might add a little insight:
http://lucene.apache.org/core/old_versioned_docs/versions/3_5_0/fileformats.html#file-names.
It's for 3.5, but the take-away is that *.fdt and *.fdx files are where a
raw copy of the data goes when you specify Store.YES. They are completely
independent of all t
