Package io.nosqlbench.engine.api.activityapi.core.ops.fluent.opfacets

package io.nosqlbench.engine.api.activityapi.core.ops.fluent.opfacets
  • Class
    Description
    CompletedOp<D>
    A CompletedOp can be any of SucceededOp FailedOp SkippedOp It may be necessary to downcast a completed Op in order to get more contextual details from it.
    EventedOpImpl<D>
     
    FailedOp<D>
    A failed op is any operation which has an error, according to the semantics of the implementing activity type.
    OpEvents<D>
     
    OpFacets<D>
    This interface represents the union of interfaces needed for all of the behavioral facets of a useful Op implementation.
    OpImpl<D>
     
    Payload<D>
    This op context carries with it a data element which a protocol-specific implementation can use to hold the state and logic for operations.
    SkippedOp<D>
     
    StartedOp<D>
    A StartedOp is a type that represents that an operation has been sent to some specific type of protocol or logic.
    SucceededOp<D>
    An op should be deemed successful if it completes with no exception.
    TrackedOp<D>
    A tracked op is one that has been added to a tracker, and can then be started.