I agree that it may be a useful test to narrow the problem down.
But given that you have deleted docs, i'm not sure what conclusions
could be drawn from it, because lots of other changes will happen too
(e.g. docs, positions, etc will compress differently).
On Fri, Feb 2, 2018 at 9:19 AM, Tony Ma
Thanks Rebert.
We are not going to use merge to repair corrupted index, the issue we are
seeing is that as a segment is already got corrupted, but merges usually run
automatically in background, I am trying to know that when this scenario
occurs, will merge stop with an exception or will merge
IMO this is not something you want to do.
The only remedy CheckIndex has for a corrupted segment is to drop it
completely: and if you choose to do that then you lose all the
documents in that segment. So its not very useful to merge it with
other segments into bigger corrupted segments since it wi
Thanks for the feedback!
-Original Message-
From: Adrien Grand [mailto:jpou...@gmail.com]
Sent: Friday, February 02, 2018 1:42 PM
To: java-user@lucene.apache.org
Subject: Re: Increase search performance
If needsScores returns false on the collector, then scores won't be computed.
Your pr
If needsScores returns false on the collector, then scores won't be
computed.
Your prototype should work well.
Le ven. 2 févr. 2018 à 04:46, Atul Bisaria a
écrit :
> Hi Adrien,
>
> Please correct if I am wrong, but I believe using extended IntComparator
> in custom Sort object for randomization
Hi experts,
A question to corrupted index. If an index segment is already corrupted, can it
be merged with another segment. Or it depends on where it got corrupted, for
example corrupted in .pay file?
From: 马江
Date: Friday, January 19, 2018 at 9:52 AM
To: "java-user@lucene.apache.org"
Subject
