Uses of Package
io.nosqlbench.engine.api.activityapi.core.ops.fluent.opfacets
Packages that use io.nosqlbench.engine.api.activityapi.core.ops.fluent.opfacets
Package
Description
-
Classes in io.nosqlbench.engine.api.activityapi.core.ops.fluent.opfacets used by io.nosqlbench.engine.api.activityapi.coreClassDescriptionA tracked op is one that has been added to a tracker, and can then be started.
-
Classes in io.nosqlbench.engine.api.activityapi.core.ops.fluent.opfacets used by io.nosqlbench.engine.api.activityapi.core.ops.fluentClassDescriptionA failed op is any operation which has an error, according to the semantics of the implementing activity type.A StartedOp is a type that represents that an operation has been sent to some specific type of protocol or logic.An op should be deemed successful if it completes with no exception.A tracked op is one that has been added to a tracker, and can then be started.
-
Classes in io.nosqlbench.engine.api.activityapi.core.ops.fluent.opfacets used by io.nosqlbench.engine.api.activityapi.core.ops.fluent.opfacetsClassDescriptionA CompletedOp can be any of
SucceededOpFailedOpSkippedOpIt may be necessary to downcast a completed Op in order to get more contextual details from it.A failed op is any operation which has an error, according to the semantics of the implementing activity type.This interface represents the union of interfaces needed for all of the behavioral facets of a useful Op implementation.This op context carries with it a data element which a protocol-specific implementation can use to hold the state and logic for operations.A StartedOp is a type that represents that an operation has been sent to some specific type of protocol or logic.An op should be deemed successful if it completes with no exception.A tracked op is one that has been added to a tracker, and can then be started. -
Classes in io.nosqlbench.engine.api.activityapi.core.ops.fluent.opfacets used by io.nosqlbench.engine.api.activityapi.cyclelog.buffers.op_outputClassDescriptionA CompletedOp can be any of
SucceededOpFailedOpSkippedOpIt may be necessary to downcast a completed Op in order to get more contextual details from it. -
Classes in io.nosqlbench.engine.api.activityapi.core.ops.fluent.opfacets used by io.nosqlbench.engine.api.activityimpl.motorClassDescriptionA CompletedOp can be any of
SucceededOpFailedOpSkippedOpIt may be necessary to downcast a completed Op in order to get more contextual details from it.A failed op is any operation which has an error, according to the semantics of the implementing activity type.A StartedOp is a type that represents that an operation has been sent to some specific type of protocol or logic.An op should be deemed successful if it completes with no exception.