Class LogByteSizeMergePolicy
This is a LogMergePolicy that measures size of a segment as the total byte size of the segment's files.
Inherited Members
Assembly: DistributedLucene.Net.dll
Syntax
public class LogByteSizeMergePolicy : LogMergePolicy
Constructors
Name | Description |
---|---|
LogByteSizeMergePolicy() | Sole constructor, setting all settings to their defaults. |
Fields
Name | Description |
---|---|
DEFAULT_MAX_MERGE_MB | Default maximum segment size. A segment of this size or larger will never be merged. |
DEFAULT_MAX_MERGE_MB_FOR_FORCED_MERGE | Default maximum segment size. A segment of this size or larger will never be merged during ForceMerge(Int32). |
DEFAULT_MIN_MERGE_MB | Default minimum segment size. |
Properties
Name | Description |
---|---|
MaxMergeMB | Determines the largest segment (measured by total byte size of the segment's files, in MB) that may be merged with other segments. Small values (e.g., less than 50 MB) 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. Note that MaxMergeDocs is also used to check whether a segment is too large for merging (it's either or). |
MaxMergeMBForForcedMerge | Determines the largest segment (measured by total byte size of the segment's files, in MB) that may be merged with other segments during forceMerge. Setting it low will leave the index with more than 1 segment, even if ForceMerge(Int32) is called. |
MinMergeMB | Sets the minimum size for the lowest level segments. Any segments below this size are considered to be on the same level (even if they vary drastically in size) and will be merged whenever there are mergeFactor of them. This effectively truncates the "long tail" of small segments that would otherwise be created into a single level. If you set this too large, it could greatly increase the merging cost during indexing (if you flush many small segments). |
Methods
Name | Description |
---|---|
Size(SegmentCommitInfo) |