Class Cqld4CoreOpMapper
java.lang.Object
io.nosqlbench.adapter.cqld4.opmappers.Cqld4BaseOpMapper<Cqld4BaseOp<?>>
io.nosqlbench.adapter.cqld4.opmappers.Cqld4CoreOpMapper
- All Implemented Interfaces:
OpMapper<Cqld4BaseOp<?>,Cqld4Space>
-
Field Summary
Fields inherited from class io.nosqlbench.adapter.cqld4.opmappers.Cqld4BaseOpMapper
adapter -
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionapply(NBComponent adapterC, ParsedOp op, LongFunction<Cqld4Space> spaceF) Determine what type of op dispenser to use for a given parsed op template, and return a new instance for it.
-
Constructor Details
-
Cqld4CoreOpMapper
-
-
Method Details
-
apply
public OpDispenser<Cqld4BaseOp<?>> apply(NBComponent adapterC, ParsedOp op, LongFunction<Cqld4Space> spaceF) Determine what type of op dispenser to use for a given parsed op template, and return a new instance for it. Since the operations under the CQL driver 4.* do not follow a common type structure, we use the base types in the NoSQLBench APIs and treat them somewhat more generically than with other drivers.- Specified by:
applyin interfaceOpMapper<Cqld4BaseOp<?>,Cqld4Space> - Specified by:
applyin classCqld4BaseOpMapper<Cqld4BaseOp<?>>- Parameters:
adapterC-op- TheParsedOpwhich is the parsed version of the user-provided op template. This contains all the fields provided by the user, as well as explicit knowledge of which ones are static and dynamic.spaceF- This is the pre-baked lambda needed to access the specificOpMapperfor a given cycle, if or when it is needed. Not all op types need this, since they may have all the state needed fully captured within the native type. For those that do, ensure that you are accessing the value through this function lazily and only within the stack. Using this function to do anything but build more lambdas is probably a programming error.- Returns:
- An op dispenser for each provided op command
-