Uses of Package
io.nosqlbench.nb.api.components.core
Packages that use io.nosqlbench.nb.api.components.core
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapter.amqpClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapter.amqp.dispensersClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapter.azureaisearchClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapter.azureaisearch.opsdispenserClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapter.cqld4ClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapter.cqld4.opdispensersClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapter.cqld4.opmappersClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapter.dataapiClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapter.dataapi.opdispensersClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapter.diagClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapter.diag.optasksClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapter.dynamodbClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapter.dynamodb.opdispensersClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapter.gcpspannerClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapter.gcpspanner.opdispensersClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapter.httpClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapter.http.coreClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapter.kafkaClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapter.kafka.dispensersClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapter.mongodb.coreClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapter.mongodb.dispensersClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapter.neo4jClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapter.neo4j.opdispensersClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapter.prototypeClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapter.prototype.dispensersClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapter.pulsarClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapter.pulsar.dispensersClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapter.qdrantClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapter.qdrant.opdispensersClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapter.s4jClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapter.s4j.dispensersClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapter.stdoutClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapter.tcpclientClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapter.tcpserverClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapter.weaviateClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapter.weaviate.opsdispensersClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapters.api.activityimplClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapters.api.activityimpl.uniformClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapters.api.activityimpl.uniform.opwrappersClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapters.api.evalctx.comparatorsClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.adapters.api.templatingClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.cqlgen.api
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.cqlgen.model
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.cqlgen.transformers
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.engine.api.activityapi.coreClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.engine.api.activityapi.errorhandlingClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.engine.api.activityapi.simrateClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.engine.api.activityimplClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.engine.api.activityimpl.inputClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.engine.api.activityimpl.uniformClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.engine.api.metricsClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.engine.cmdstreamClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.engine.core.clientloadClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.engine.core.lifecycleClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.engine.core.lifecycle.activityClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.engine.core.lifecycle.commandsClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.engine.core.lifecycle.commands.fortestingClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.engine.core.lifecycle.scenario.containerClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.engine.core.lifecycle.scenario.executionClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.engine.core.lifecycle.scenario.scriptClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.engine.core.lifecycle.sessionClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.engine.extensions.computefunctionsClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.engine.extensions.exampleClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.engine.extensions.globalvarsClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.engine.extensions.vectormathClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.nb.api.advisorClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.nb.api.components.coreClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
errored_at > 0 -> ERROR started_at == 0 -> STARTING <p> <p> <p> started_at > closed_at STARTING closed_at > started_at RUNNING teardown_at > closed_at STOPPING teardown_at STOPPED stopped_atBecause of ctor super calling order requirements, the task thread can't always be started automatically in super(...). -
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.nb.api.components.eventsClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.nb.api.components.statusClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
errored_at > 0 -> ERROR started_at == 0 -> STARTING <p> <p> <p> started_at > closed_at STARTING closed_at > started_at RUNNING teardown_at > closed_at STOPPING teardown_at STOPPED stopped_atBecause of ctor super calling order requirements, the task thread can't always be started automatically in super(...). -
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.nb.api.config.standardClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.nb.api.csvoutputClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.nb.api.engine.activityimpl
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.nb.api.engine.metricsClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.nb.api.engine.metrics.instrumentsClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.nb.api.engine.metrics.reportersClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.Because of ctor super calling order requirements, the task thread can't always be started automatically in super(...).
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.nb.api.engine.metrics.wrappersClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.nb.api.extensionsClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.nb.api.histoClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.nb.api.httpClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.nb.api.loadersClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.nb.api.optimizersClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.nb.api.s3uploaderClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.nb.api.shutdownClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.nb.api.taggingClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.scenarios.diagClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.scenarios.simframe.optimizersClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.scenarios.simframe.optimizers.findmaxClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.scenarios.simframe.optimizers.optimoClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.scenarios.simframe.optimizers.planners.findmaxClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.scenarios.simframe.optimizers.planners.ratchetClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.scenarios.simframe.optimizers.planners.rcurveClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.
-
Classes in io.nosqlbench.nb.api.components.core used by io.nosqlbench.scenarios.simframe.planningClassDescriptionA Component is a functional element of the NoSQLBench runtime which is: Contract Oriented - Components are based on well-defined interfaces. Modular - Components are wired together by configuration. Configurable - Components have configurations which are well defined and type safe. User Facing - Components are top level constructs which users interact with. Hierarchic - Components fit together in a runtime hierarchy.This is the stateful store of metrics on a specific component in the hierarchy.