The LogDocMergePolicy type exposes the following members.
Methods
| Name | Description | |
|---|---|---|
 | Close | (Inherited from LogMergePolicy.) |
| Equals | (Inherited from Object.) |
 | Finalize | Allows an Object to attempt to free resources and perform other cleanup operations before the Object is reclaimed by garbage collection. (Inherited from Object.) |
| FindMerges | Checks if any merges are now necessary and returns a
{@link MergePolicy.MergeSpecification} if so. A merge
is necessary when there are more than {@link
#setMergeFactor} segments at a given level. When
multiple levels have too many segments, this method
will return multiple merges, allowing the {@link
MergeScheduler} to use concurrency.
(Inherited from LogMergePolicy.) |
| FindMergesForOptimize | Returns the merges necessary to optimize the index.
This merge policy defines "optimized" to mean only one
segment 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 {@link MergeScheduler}
in use may make use of concurrency.
(Inherited from LogMergePolicy.) |
| FindMergesToExpungeDeletes | Finds merges necessary to expunge all deletes from the
index. We simply merge adjacent segments that have
deletes, up to mergeFactor at a time.
(Inherited from LogMergePolicy.) |
| GetCalibrateSizeByDeletes | Returns true if the segment size should be calibrated
by the number of deletes when choosing segments for merge.
(Inherited from LogMergePolicy.) |
| GetHashCode | Serves as a hash function for a particular type. (Inherited from Object.) |
| GetMaxMergeDocs | Returns the largest segment (measured by document
count) that may be merged with other segments.
(Inherited from LogMergePolicy.) |
| GetMergeFactor | Returns the number of segments that are merged at
once and also controls the total number of segments
allowed to accumulate in the index. (Inherited from LogMergePolicy.) |
| GetMinMergeDocs | Get the minimum size for a segment to remain
un-merged.
|
| GetNoCFSRatio | (Inherited from LogMergePolicy.) |
| GetType | Gets the Type of the current instance. (Inherited from Object.) |
| GetUseCompoundDocStore | Returns true if newly flushed and newly merge doc
store segment files (term vectors and stored fields)
(Inherited from LogMergePolicy.) |
| GetUseCompoundFile | Returns true if newly flushed and newly merge segments (Inherited from LogMergePolicy.) |
| MakeOneMerge | (Inherited from LogMergePolicy.) |
| MemberwiseClone | Creates a shallow copy of the current Object. (Inherited from Object.) |
| SetCalibrateSizeByDeletes | Sets whether the segment size should be calibrated by
the number of deletes when choosing segments for merge.
(Inherited from LogMergePolicy.) |
| SetMaxMergeDocs | 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 {@link Integer#MAX_VALUE}.The default merge policy ({@link
LogByteSizeMergePolicy}) also allows you to set this
limit by net size (in MB) of the segment, using {@link
LogByteSizeMergePolicy#setMaxMergeMB}. (Inherited from LogMergePolicy.) |
| SetMergeFactor | Determines how often segment indices are merged by
addDocument(). With smaller values, less RAM is used
while indexing, and searches on unoptimized indices are
faster, but indexing speed is slower. With larger
values, more RAM is used during indexing, and while
searches on unoptimized indices are slower, indexing is
faster. Thus larger values (> 10) are best for batch
index creation, and smaller values (< 10) for indices
that are interactively maintained.
(Inherited from LogMergePolicy.) |
| SetMinMergeDocs | 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).
|
| SetNoCFSRatio | (Inherited from LogMergePolicy.) |
| SetUseCompoundDocStore | Sets whether compound file format should be used for
newly flushed and newly merged doc store
segment files (term vectors and stored fields).
(Inherited from LogMergePolicy.) |
| SetUseCompoundFile | Sets whether compound file format should be used for
newly flushed and newly merged segments.
(Inherited from LogMergePolicy.) |
| Size | (Overrides LogMergePolicy..::..Size(SegmentInfo).) |
| SizeBytes | (Inherited from LogMergePolicy.) |
| SizeDocs | (Inherited from LogMergePolicy.) |
| ToString | (Inherited from Object.) |
| UseCompoundDocStore | (Inherited from LogMergePolicy.) |
| UseCompoundFile | (Inherited from LogMergePolicy.) |
| Verbose | (Inherited from LogMergePolicy.) |
