Uses of Class
org.hibernate.search.engine.backend.work.execution.OperationSubmitter

Packages that use OperationSubmitter

Package	Description
org.hibernate.search.engine.backend.orchestration.spi
org.hibernate.search.engine.backend.schema.management.spi
org.hibernate.search.engine.backend.work.execution
org.hibernate.search.engine.backend.work.execution.spi

Uses of OperationSubmitter in org.hibernate.search.engine.backend.orchestration.spi

Methods in org.hibernate.search.engine.backend.orchestration.spi with parameters of type OperationSubmitter

Modifier and Type	Method	Description
protected abstract void	AbstractWorkOrchestrator.doSubmit(W work, OperationSubmitter operationSubmitter)
final void	AbstractWorkOrchestrator.submit(W work, OperationSubmitter operationSubmitter)
void	BatchingExecutor.submit(W work, OperationSubmitter operationSubmitter)	Submit a work for execution.

Uses of OperationSubmitter in org.hibernate.search.engine.backend.schema.management.spi

Methods in org.hibernate.search.engine.backend.schema.management.spi with parameters of type OperationSubmitter

Modifier and Type	Method	Description
CompletableFuture<?>	IndexSchemaManager.createIfMissing(OperationSubmitter operationSubmitter)	Creates the schema if it doesn't already exist.
CompletableFuture<?>	IndexSchemaManager.createOrUpdate(OperationSubmitter operationSubmitter)	Creates the schema if it doesn't already exist, or updates the existing schema to match requirements expressed by the mapper.
CompletableFuture<?>	IndexSchemaManager.createOrValidate(ContextualFailureCollector failureCollector, OperationSubmitter operationSubmitter)	Creates the schema if it doesn't already exist, or validates the existing schema against requirements expressed by the mapper.
CompletableFuture<?>	IndexSchemaManager.dropAndCreate(OperationSubmitter operationSubmitter)	Drops the schema and all indexed data if it exists, then creates the schema.
CompletableFuture<?>	IndexSchemaManager.dropIfExisting(OperationSubmitter operationSubmitter)	Drops the schema and all indexed data if it exists.
CompletableFuture<?>	IndexSchemaManager.validate(ContextualFailureCollector failureCollector, OperationSubmitter operationSubmitter)	Validates the existing schema against requirements expressed by the mapper.

Uses of OperationSubmitter in org.hibernate.search.engine.backend.work.execution

Methods in org.hibernate.search.engine.backend.work.execution that return OperationSubmitter

Modifier and Type	Method	Description
static OperationSubmitter	OperationSubmitter.blocking()	When using this submitter, dding a new element will block the thread when the underlying queue is a BlockingQueue and it is at its maximum capacity, until some elements are removed from the queue
static OperationSubmitter	OperationSubmitter.offloading(Consumer<Runnable> executor)	Creates an operation submitter that would attempt to submit work to a queue, but in case the queue is full it would offload the submitting of the operation to provided executor.
static OperationSubmitter	OperationSubmitter.rejecting()	When using this submitter adding a new element will cause a RejectedExecutionException when the underlying queue is a BlockingQueue and it is at its maximum capacity.

Uses of OperationSubmitter in org.hibernate.search.engine.backend.work.execution.spi

Methods in org.hibernate.search.engine.backend.work.execution.spi with parameters of type OperationSubmitter

Modifier and Type	Method	Description
CompletableFuture<?>	IndexIndexer.add(DocumentReferenceProvider referenceProvider, DocumentContributor documentContributor, DocumentCommitStrategy commitStrategy, DocumentRefreshStrategy refreshStrategy, OperationSubmitter operationSubmitter)	Add a document to the index, assuming that the document is absent from the index.
CompletableFuture<?>	IndexIndexer.addOrUpdate(DocumentReferenceProvider referenceProvider, DocumentContributor documentContributor, DocumentCommitStrategy commitStrategy, DocumentRefreshStrategy refreshStrategy, OperationSubmitter operationSubmitter)	Update a document in the index, or add it if it's absent from the index.
CompletableFuture<?>	IndexIndexer.delete(DocumentReferenceProvider referenceProvider, DocumentCommitStrategy commitStrategy, DocumentRefreshStrategy refreshStrategy, OperationSubmitter operationSubmitter)	Delete a document from the index.
default CompletableFuture<?>	IndexIndexingPlan.execute(OperationSubmitter operationSubmitter)	Start executing all the works in this plan, and clear the plan so that it can be re-used.
CompletableFuture<MultiEntityOperationExecutionReport>	IndexIndexingPlan.executeAndReport(OperationSubmitter operationSubmitter)	Start executing all the works in this plan, and clear the plan so that it can be re-used.
CompletableFuture<?>	IndexWorkspace.flush(OperationSubmitter operationSubmitter)
CompletableFuture<?>	IndexWorkspace.mergeSegments(OperationSubmitter operationSubmitter)
CompletableFuture<?>	IndexWorkspace.purge(Set<String> routingKeys, OperationSubmitter operationSubmitter)
CompletableFuture<?>	IndexWorkspace.refresh(OperationSubmitter operationSubmitter)