Class LogMergePolicy

Sole constructor. (For invocation by subclass constructors, typically implicit.)

Default maximum segment size. A segment of this size or larger will never be merged.

Default merge factor, which is how many segments are merged at a time

Default noCFSRatio. If a merge's size is >= 10% of the index, then we disable compound file for it.

Defines the allowed range of log(size) for each level. A level is computed by taking the max segment log size, minus LEVEL_LOG_SPAN, and finding all segments falling within that range.

If true, we pro-rate a segment's size by the percentage of non-deleted documents.

If a segment has more than this many documents then it will never be merged.

If the size of a segment exceeds this value then it will never be merged.

If the size of a segment exceeds this value then it will never be merged during ForceMerge(Int32).

How many segments to merge at a time.

Any segments whose size is smaller than this value will be rounded up to this value. This ensures that tiny segments are aggressively merged.

Gets or Sets whether the segment size should be calibrated by the number of deletes when choosing segments for merge.

Returns true if LogMergePolicy is enabled in Lucene.Net.Index.IndexWriter.infoStream.

Determines the largest segment (measured by document count) that may be merged with other segments. Small values (e.g., less than 10,000) are best for interactive indexing, as this limits the length of pauses while indexing to a few seconds. Larger values are best for batched indexing and speedier searches.

The default value is .

The default merge policy (LogByteSizeMergePolicy) also allows you to set this limit by net size (in MB) of the segment, using MaxMergeMB.

Gets or Sets the number of segments that are merged at once and also controls the total number of segments allowed to accumulate in the index.

This determines how often segment indices are merged by AddDocument(IEnumerable<IIndexableField>). With smaller values, less RAM is used while indexing, and searches are faster, but indexing speed is slower. With larger values, more RAM is used during indexing, and while searches is slower, indexing is faster. Thus larger values (> 10) are best for batch index creation, and smaller values (< 10) for indices that are interactively maintained.

Finds merges necessary to force-merge all deletes from the index. We simply merge adjacent segments that have deletes, up to mergeFactor at a time.

Returns the merges necessary to merge the index down to a specified number of segments. this respects the m_maxMergeSizeForForcedMerge setting. By default, and assuming maxNumSegments=1, only one segment will be left in the index, where that segment has no deletions pending nor separate norms, and it is in compound file format if the current useCompoundFile setting is true. This method returns multiple merges (mergeFactor at a time) so the MergeScheduler in use may make use of concurrency.

Checks if any merges are now necessary and returns a MergePolicy.MergeSpecification if so. A merge is necessary when there are more than MergeFactor segments at a given level. When multiple levels have too many segments, this method will return multiple merges, allowing the MergeScheduler to use concurrency.

Returns true if the number of segments eligible for merging is less than or equal to the specified maxNumSegments.

Print a debug message to Lucene.Net.Index.IndexWriter.infoStream.

Return the byte size of the provided SegmentCommitInfo, pro-rated by percentage of non-deleted documents if CalibrateSizeByDeletes is set.

Return the number of documents in the provided SegmentCommitInfo, pro-rated by percentage of non-deleted documents if CalibrateSizeByDeletes is set.