it appears Lucene 5.2 index merge is running checkIntegrity on existing
index prior to merging additional indices.
This seems to be new.
We have an existing checkIndex but this is run post index merge.
Two follow up questions :
* Is there way to turn off built-in checkIntegrity? Just for my under
We observe some merge slowness after we migrated from 4.10 to 5.2.
Is this expected? Any new tunable merge parameters in Lucene 5 ?
-Selva
There is a Class org.apache.lucene.codecs.blocktree.BlockTreeTermsWriter
which have two parameters,one is DEFAULT_MIN_BLOCK_SIZE,the other is
DEFAULT_MAX_BLOCK_SIZE;their default values is 25 and 48；when I
make their values to bigger,for example,200 and 398；And then to make index，the
result
Hi Alan,
Thank you for your answer: it is exactly what I need.
Regards,
Aurélien
On 12.09.2015 11:21, Alan Woodward wrote:
> If you're using lucene 5.3, you could create a modified version of
> PayloadScoreQuery that just uses positions rather than payloads to modify the
> score.
>
