LiveIndexWriterConfig

if an indexing thread should check for pending flushes on update in order to help out on a full flush

Codec used to write new segments.

True if calls to IndexWriter.close should first do a commit.

Compatibility version to use for this index.

FlushPolicy to control when segments are flushed.

The sort order to use to write merged segments.

The field names involved in the index sort

InfoStream for debugging messages.

The comparator for sorting leaf readers.

Returns the number of buffered added documents that will trigger a flush if enabled.

Amount of time to wait for merges returned by MergePolicy.findFullFlushMerges(...)

MergePolicy for selecting merges.

MergeScheduler to use for running merges.

OpenMode that IndexWriter is opened with.

parent document field

Returns the value set by .setRAMBufferSizeMB if enabled.

Sets the hard upper bound on RAM usage for a single segment, after which the segment is forced to flush.

True if readers should be pooled.

Similarity to use when encoding norms.

soft deletes field

True if segment flushes should use compound file format

Returns the current merged segment warmer. See IndexReaderWarmer.

Expert: sets if indexing threads check for pending flushes on update in order to help our flushing indexing buffers to disk. As a consequence, threads calling or IndexWriter.flush will be the only thread writing segments to disk unless flushes are falling behind. If indexing is stalled due to too many pending flushes indexing threads will help our writing pending segment flushes to disk.

Determines the minimal number of documents required before the buffered in-memory documents are flushed as a new Segment. Large values generally give faster indexing.

Set the merged segment warmer. See IndexReaderWarmer.

Expert: MergePolicy is invoked whenever there are changes to the segments in the index. Its role is to select which merges to do, if any, and return a [ ] describing the merges. It also selects merges to do for forceMerge.

Determines the amount of RAM that may be used for buffering added documents and deletions before they are flushed to the Directory. Generally for faster indexing performance it's best to flush by RAM usage instead of document count and use as large a RAM buffer as you can.

Sets if the IndexWriter should pack newly written segments in a compound file. Default is true.