Hi Simon, guys,
I see LUCENE-5038, useCompoundFile stuff had been refactored. Now I think
there are some problems with LogMergePolicy.
Example:
1. setting useCompoundFile as false and no changing NOCFSRatio(1.0 by
default).
2. starting index, new segment will not use compound file even it's small
Can you turn on IndexWriter's infoStream and post the resulting output?
Enabling calibrateSizeByDeletes doesn't automatically mean that
segments with many deletes will be merged. EG if your mergeFactor is
high relative to the number of segments you have at each level, then
no merging will take
Hello,
I am in the process of trying out the lucene patch LUCENE-1634,
however I'm not getting the expected behavior.
I see that the segments are not getting merged even after all the
documents are deleted from it.
Because of this, the index size really grows to a huge number. The
Hello,
I'm curious, why is LogMergePolicy named *Log*MergePolicy?
(Why not ExpMergePolicy? :-)
Thank you,
Koji
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I'm curious, why is LogMergePolicy named *Log*MergePolicy?
(Why not ExpMergePolicy? :-)
Well, I guess it's a matter of perspective. When you look at the way the
algorithm works, the merge decisions are based on a concept of level and
levels are assigned based on the log
On Jan 24, 2008 8:40 AM, Steven Parkes [EMAIL PROTECTED] wrote:
I'm curious, why is LogMergePolicy named *Log*MergePolicy?
(Why not ExpMergePolicy? :-)
Well, I guess it's a matter of perspective. When you look at the way the
algorithm works, the merge decisions are based
Thank you Steven and Yonik,
I think I got it. And I can find LogMergePolicy uses
Math.log() to find merges. :-)
Thank you again,
Koji
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
