sanitize nosqlbench terminology

This commit is contained in:
phact 2020-03-05 17:08:35 -05:00
parent 900a006e82
commit ff612e9bbf
5 changed files with 16 additions and 16 deletions

View File

@ -35,7 +35,7 @@ activity types.
- **driver** - default: dse - The type of driver to use, either dse, or
oss. If you need DSE-specific features, use the dse driver. If you are
connecting to an OSS Apache Cassandra cluster, you must use the oss
driver. The oss driver option is only available in ebdse.
driver. The oss driver option is only available in nosqlbench.
- **host** - The host or hosts to use for connection points to
the cluster. If you specify multiple values here, use commas
with no spaces.
@ -213,7 +213,7 @@ activity types.
The clusterid specified is included so that separate cluster and session
contexts can be reported independently for advanced tests.
- **usercodecs** - enable the loading of user codec libraries
for more details see: com.datastax.codecs.framework.UDTCodecInjector in the ebdse
for more details see: com.datastax.codecs.framework.UDTCodecInjector in the nosqlbench
code base. This is for dynamic codec loading with user-provided codecs mapped
via the internal UDT APIs.
default: false
@ -394,4 +394,4 @@ There is a basic example below that can be copied as a starting template.
## YAML Examples
Please see the bundled activities with ebdse for examples.
Please see the bundled activities with nosqlbench for examples.

View File

@ -61,7 +61,7 @@ When an error occurs, you can control how it is handled for the most part.
This is the error handler stack:
- **stop** - logs an error, and then rethrows the causing exception,
causing ebdse to shutdown the current scenario.
causing nosqlbench to shutdown the current scenario.
- **warn** - log a warning in the log, with details about the error
and associated statement.
- **retry** - Retry the operation if the number of retries hasn't been
@ -99,15 +99,15 @@ handler assigned to it.
The errors that can be handled are simply all the exception types that
can be thrown by either the DataStax Java Driver for DSE, *or* the
ebdse client itself. This includes errors that indicate a potentially
nosqlbench client itself. This includes errors that indicate a potentially
intermittent failure condition. It also includes errors that are more
permanent in nature, like WriteFailure, which would continue to occur
on subsequent retries without some form of intervention. The ebdse
on subsequent retries without some form of intervention. The nosqlbench
application will also generate some additional exceptions that capture
common error cases that the Java driver doesn't or shouldn't have a
special case for, but which may be important for ebdse testing purposes.
special case for, but which may be important for nosqlbench testing purposes.
In ebdse, all error handlers are specific to a particular kind of
In nosqlbench, all error handlers are specific to a particular kind of
exception that you would catch in a typical application that uses DSE,
although you can tell a handler to take care of a whole category
of problems as long as you know the right name to use.
@ -178,7 +178,7 @@ with the default configuration shown.
##### Additional Exceptions
The following exceptions are synthesized directly by ebdse, but get
The following exceptions are synthesized directly by nosqlbench, but get
handled alongside the normal exceptions as explained above.
1. ChangeUnappliedException - The change unapplied condition is important to

View File

@ -124,7 +124,7 @@ Verify the the same 100K cycles of telemetry data
... run type=cqlverify alias=verify yaml=telemetry tags=group:verify cycles=100000 host=...
To see how these examples work, consult the telemetry.yaml file in the ebdse.jar.
To see how these examples work, consult the telemetry.yaml file in the nosqlbench.jar.
### CQLVerify ActivityType Parameters

View File

@ -51,7 +51,7 @@ activity types.
- **driver** - default: dse - The type of driver to use, either dse, or
oss. If you need DSE-specific features, use the dse driver. If you are
connecting to an OSS Apache Cassandra cluster, you must use the oss
driver. The oss driver option is only available in ebdse.
driver. The oss driver option is only available in nosqlbench.
- **host** - The host or hosts to use for connection points to
the cluster. If you specify multiple values here, use commas
with no spaces.
@ -229,7 +229,7 @@ activity types.
The clusterid specified is included so that separate cluster and session
contexts can be reported independently for advanced tests.
- **usercodecs** - enable the loading of user codec libraries
for more details see: com.datastax.codecs.framework.UDTCodecInjector in the ebdse
for more details see: com.datastax.codecs.framework.UDTCodecInjector in the nosqlbench
code base. This is for dynamic codec loading with user-provided codecs mapped
via the internal UDT APIs.
default: false
@ -410,4 +410,4 @@ There is a basic example below that can be copied as a starting template.
## YAML Examples
Please see the bundled activities with ebdse for examples.
Please see the bundled activities with nosqlbench for examples.

View File

@ -51,7 +51,7 @@ activity types.
- **driver** - default: dse - The type of driver to use, either dse, or
oss. If you need DSE-specific features, use the dse driver. If you are
connecting to an OSS Apache Cassandra cluster, you must use the oss
driver. The oss driver option is only available in ebdse.
driver. The oss driver option is only available in nosqlbench.
- **host** - The host or hosts to use for connection points to
the cluster. If you specify multiple values here, use commas
with no spaces.
@ -229,7 +229,7 @@ activity types.
The clusterid specified is included so that separate cluster and session
contexts can be reported independently for advanced tests.
- **usercodecs** - enable the loading of user codec libraries
for more details see: com.datastax.codecs.framework.UDTCodecInjector in the ebdse
for more details see: com.datastax.codecs.framework.UDTCodecInjector in the nosqlbench
code base. This is for dynamic codec loading with user-provided codecs mapped
via the internal UDT APIs.
default: false
@ -410,4 +410,4 @@ There is a basic example below that can be copied as a starting template.
## YAML Examples
Please see the bundled activities with ebdse for examples.
Please see the bundled activities with nosqlbench for examples.