Uses of Interface
io.nosqlbench.engine.api.activityapi.cyclelog.buffers.results.CycleReadable
Packages that use CycleReadable
Package
Description
-
Uses of CycleReadable in io.nosqlbench.engine.api.activityapi.core.ops.fluent.opfacets
Subinterfaces of CycleReadable in io.nosqlbench.engine.api.activityapi.core.ops.fluent.opfacetsModifier and TypeInterfaceDescriptioninterfaceCompletedOp<D>A CompletedOp can be any ofSucceededOpFailedOpSkippedOpIt may be necessary to downcast a completed Op in order to get more contextual details from it.interfaceFailedOp<D>A failed op is any operation which has an error, according to the semantics of the implementing activity type.interfaceOpFacets<D>This interface represents the union of interfaces needed for all of the behavioral facets of a useful Op implementation.interfaceSkippedOp<D>interfaceStartedOp<D>A StartedOp is a type that represents that an operation has been sent to some specific type of protocol or logic.interfaceSucceededOp<D>An op should be deemed successful if it completes with no exception.interfaceTrackedOp<D>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 that implement CycleReadable -
Uses of CycleReadable in io.nosqlbench.engine.api.activityapi.cyclelog.buffers.results
Subinterfaces of CycleReadable in io.nosqlbench.engine.api.activityapi.cyclelog.buffers.resultsModifier and TypeInterfaceDescriptioninterfaceinterfaceA readable interface for (cycle, result) tuple types.Classes in io.nosqlbench.engine.api.activityapi.cyclelog.buffers.results that implement CycleReadable