Examples of SnapshotDeletionPolicy

org.apache.lucene.index.SnapshotDeletionPolicy

A {@link IndexDeletionPolicy} that wraps around any other{@link IndexDeletionPolicy} and adds the ability to hold andlater release a single "snapshot" of an index. While the snapshot is held, the {@link IndexWriter} will notremove any files associated with it even if the index is otherwise being actively, arbitrarily changed. Because we wrap another arbitrary {@link IndexDeletionPolicy}, this gives you the freedom to continue using whatever {@link IndexDeletionPolicy} you would normally want to use with yourindex. Note that you can re-use a single instance of SnapshotDeletionPolicy across multiple writers as long as they are against the same index Directory. Any snapshot held when a writer is closed will "survive" when the next writer is opened.

WARNING: This API is a new and experimental and may suddenly change.

org.elasticsearch.index.deletionpolicy.SnapshotDeletionPolicy

Snapshot deletion policy allows to get snapshots of an index state (last commit or all commits) and if the deletion policy is used with all open index writers (JVM level) then the snapshot state will not be deleted until it will be released. @author kimchy (shay.banon)

    protected IndexDeletionPolicy createIndexDeletionPolicy() {
        return new KeepOnlyLastDeletionPolicy(shardId, EMPTY_SETTINGS);
    }


    protected SnapshotDeletionPolicy createSnapshotDeletionPolicy() {
        return new SnapshotDeletionPolicy(createIndexDeletionPolicy());
    }

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.

Examples of SnapshotDeletionPolicy

Examples of org.elasticsearch.index.deletionpolicy.SnapshotDeletionPolicy