
io.nosqlbench.adapter.diag.optasks.DiagTask Maven / Gradle / Ivy
/*
* Copyright (c) 2022 nosqlbench
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
package io.nosqlbench.adapter.diag.optasks;
import io.nosqlbench.api.config.NBNamedElement;
import io.nosqlbench.api.config.standard.NBReconfigurable;
import io.nosqlbench.api.config.standard.NBConfigurable;
import java.util.Map;
import java.util.function.BiFunction;
/**
* The base type for building Diagnostic Op tasks, which are composed into
* a diagnostic operation in order. This allows for a very flexible compositional
* structure which can be extended as needed. The diag driver is meant to
* be the core driver for the purposes of validating the NoSQLBench engine
* and associated libraries and extensions.
*
* The tasks are retained as shared across threads by default. This means that if
* you want to have per-thread logic or to do things which are not thread-safe,
* you need to use ThreadLocal or some other pattern to do so.
*
* Tasks must provide a no-args constructor (or no constructor, which does the same).
* Tasks must specify their configuration requirements via the {@link NBConfigurable}
* interface.
*
* Tasks may be evented for updates from the activity params at runtime by implementing
* the {@link NBReconfigurable} interface.
*/
public interface DiagTask extends
BiFunction, Map>,
NBConfigurable,
NBNamedElement
{
Map apply(Long cycle, Map opstate);
}
© 2015 - 2025 Weber Informatics LLC | Privacy Policy