LogByteSizeMergePolicy (and LogDocMergePolicy) will preserve the total order.
Only TieredMergePolicy merges out-of-order segments.
I don't understand why you need to encouraging merging of the more
recent (by your "time" field) segments...
Mike McCandless
http://blog.mikemccandless.com
On Fri
Mike,
Each of my flushed segment is fully ordered by time. But TieredMergePolicy
or LogByteSizeMergePolicy is going to pick arbitrary time-segments and
disturb this arrangement and I wanted some kind of control on this.
But like you pointed-out, going by only be time-adjacent merges can be
disast
Thank you very much Mr. Shai for all your help :)
I will follow the same :)
Thank you once again :)
Regards,
Jebarlin.R
On Fri, Feb 7, 2014 at 5:05 PM, Shai Erera wrote:
> Hi
>
> Since 4.2 the facets module has gone under major changes, both API and
> implementation and performance has improve
Lucene is normally fully concurrent during searching and indexing, so
it should not 'choke' when there are multiple searches in flight.
Try getting a thread dump to see where each search is spending its effort?
What Directory implementation, OS, filesystem, JVM are you using?
Mike McCandless
ht
You want to focus merging on the segments containing newer documents?
Why? This seems somewhat dangerous...
Not taking into account the "true" segment size can lead to very very
poor merge decisions ... you should turn on IndexWriter's infoStream
and do a long running test to convince yourself th
Hi
Since 4.2 the facets module has gone under major changes, both API and
implementation and performance has improved x4. If you want to upgrade,
then I recommend waiting for 4.7 since we overhauled the API again - this
will save you the efforts to migrate to e.g 4.6 and then to the new API
once 4
