Policy for committing changesets.
Pile work operations No thread safety has to be implemented, the queue being scoped already The implementation must be "stateless" wrt the queue through (ie not store the queue state) FIXME this Interface does not make much sense, since the impl will not be changed
Sends a single operation to the related backends, considering the sharding strategy.
Visitor interface to apply the configured sharding strategy to a list of LuceneWork; this list is usually the set of operations to be applied in a transactional context.
Represents the synchronization work done when a transaction is committed or rollbacked.
Batch work until
This class provides means to convert all (by default) supported DeletionQueries back to Lucene Queries and to their String representation and back.
Implementation of the transactional context on top of an EventSource (Session)
Execute final work inside a transaction.
Queue works per transaction.
Execute final work in the after transaction synchronization.
This visitor applies the selection logic from the plugged IndexShardingStrategies to stream operations, as used by optimize() and batching operations.
This visitor applies the selection logic from the plugged IndexShardingStrategies to transactional operations, so similar to StreamingSelectionVisitor but preparing a context bound list of operations instead of sending all changes directly to the backend.
Copyright © 2006-2017 Red Hat, Inc. All Rights Reserved