Interface IndexDeletionPolicy
Expert: policy for deletion of stale Index
Implement this interface, and pass it to one
of the Index
One expected use case for this (and the reason why it
was first created) is to work around problems with an
index directory accessed via filesystems like NFS because
NFS does not provide the "delete on last close" semantics
that Lucene's "point in time" search normally relies on.
By implementing a custom deletion policy, such as "a
commit is only removed once it has been stale for more
than X minutes", you can give your readers time to
refresh to the new commit before Index
Namespace:
Assembly: Lucene.Net.NetCore.dll
Syntax
public interface IndexDeletionPolicy
Methods
Name | Description |
---|---|
OnCommit<T>(IList<T>) | This is called each time the writer completed a commit. This gives the policy a chance to remove old commit points with each commit. The policy may now choose to delete old commit points
by calling method Delete()
of Index This method is only called when Commit() or Close() is called, or possibly not at all if the Rollback() is called. Note: the last CommitPoint is the most recent one, i.e. the "front index state". Be careful not to delete it, unless you know for sure what you are doing, and unless you can afford to lose the index content while doing that. |
OnInit<T>(IList<T>) | This is called once when a writer is first instantiated to give the policy a chance to remove old commit points.
The writer locates all index commits present in the
index directory and calls this method. The policy may
choose to delete some of the commit points, doing so by
calling method Delete()
of Index
Note: the last CommitPoint is the most recent one, i.e. the "front index state". Be careful not to delete it, unless you know for sure what you are doing, and unless you can afford to lose the index content while doing that. |