Merge pull request #915 from nosqlbench/my-cql-astra-example

Security Fix by removing CompatibilityFixups

adapter-cqld4/src/main/resources/activities/baselines/cql-keyvalue-astra.md

@@ -0,0 +1,77 @@
+---
+title: CQL Key-Value
+weight: 1
+---
+
+## Description
+
+The CQL Key-Value workload demonstrates the simplest possible schema with payload data. This is useful for measuring
+system capacity most directly in terms of raw operations. As a reference point, provides some insight around types of
+workloads that are constrained around messaging, threading, and tasking, rather than bulk throughput.
+
+During preload, all keys are set with a value. During the main phase of the workload, random keys from the known
+population are replaced with new values which never repeat. During the main phase, random partitions are selected for
+upsert, with row values never repeating.
+
+## Operations
+
+### insert (rampup, main)
+
+    insert into baselines.keyvalue (key, value) values (?,?);
+
+### read (main)
+
+    select * from baselines.keyvalue where key=?key;
+
+## Data Set
+
+### baselines.keyvalue insert (rampup)
+
+- key - text, number as string, selected sequentially up to keycount
+- value - text, number as string, selected sequentially up to valuecount
+
+### baselines.keyvalue insert (main)
+
+- key - text, number as string, selected uniformly within keycount
+- value - text, number as string, selected uniformly within valuecount
+
+### baselines.keyvalue read (main)
+
+- key - text, number as string, selected uniformly within keycount
+
+## Workload Parameters
+
+This workload has no adjustable parameters when used in the baseline tests.
+
+When used for additional testing, the following parameters should be supported:
+
+- keycount - the number of unique keys
+- valuecount - the number of unique values
+
+## Key Performance Metrics
+
+Client side metrics are a more accurate measure of the system behavior from a user's perspective. For microbench and
+baseline tests, these are the only required metrics. When gathering metrics from multiple server nodes, they should be
+kept in aggregate form, for min, max, and average for each time interval in monitoring. For example, the avg p99 latency
+for reads should be kept, as well as the min p99 latency for reads. If possible metrics, should be kept in plot form,
+with discrete histogram values per interval.
+
+### Client-Side
+
+- read ops/s
+- write ops/s
+- read latency histograms
+- write latency histograms
+- exception counts
+
+### Server-Side
+
+- pending compactions
+- bytes compacted
+- active data on disk
+- total data on disk
+
+# Notes on Interpretation
+
+Once the average ratio of overwrites starts to balance with the rate of compaction, a steady state should be achieved.
+At this point, pending compactions and bytes compacted should be mostly flat over time.

adapter-cqld4/src/main/resources/activities/baselines/cql-keyvalue-astra.yaml

@@ -0,0 +1,96 @@
+description: A workload with only text keys and text values
+
+scenarios:
+  default:
+    schema: run driver=cql tags==phase:schema threads==1 cycles==UNDEF
+    rampup: run driver=cql tags==phase:rampup cycles===TEMPLATE(rampup-cycles,10000000) threads=auto
+    main: run driver=cql tags==phase:main cycles===TEMPLATE(main-cycles,10000000) threads=auto
+  astra:
+    schema: run driver=cql tags==phase:schema-astra threads==1 cycles==UNDEF
+    rampup: run driver=cql tags==phase:rampup cycles===TEMPLATE(rampup-cycles,10000000) threads=auto
+    main: run driver=cql tags==phase:main cycles===TEMPLATE(main-cycles,10000000) threads=auto
+
+bindings:
+  seq_key: Mod(<<keycount:1000000000>>); ToString() -> String
+  seq_value: Hash(); Mod(<<valuecount:1000000000>>); ToString() -> String
+  rw_key: <<keydist:Uniform(0,1000000000)->int>>; ToString() -> String
+  rw_value: Hash(); <<valdist:Uniform(0,1000000000)->int>>; ToString() -> String
+
+blocks:
+  - name: schema
+    tags:
+      phase: schema
+    params:
+      prepared: false
+    statements:
+    - create-table: |
+        create table if not exists <<keyspace:baselines>>.<<table:keyvalue>> (
+        key text,
+         value text,
+         PRIMARY KEY (key)
+        );
+      tags:
+        name: create-table
+  - name: schema-astra
+    tags:
+      phase: schema-astra
+    params:
+      prepared: false
+    statements:
+    - create-table: |
+        create table if not exists <<keyspace:baselines>>.<<table:keyvalue>> (
+        key text,
+         value text,
+         PRIMARY KEY (key)
+        );
+      tags:
+        name: create-table-astra
+  - name: rampup
+    tags:
+      phase: rampup
+    params:
+      cl: <<write_cl:LOCAL_QUORUM>>
+    statements:
+      - rampup-insert: |
+          insert into <<keyspace:baselines>>.<<table:keyvalue>>
+          (key, value)
+          values ({seq_key},{seq_value});
+        tags:
+           name: rampup-insert
+  - name: verify
+    tags:
+      phase: verify
+      type: read
+    params:
+      cl: <<read_cl:LOCAL_QUORUM>>
+    statements:
+      - verify-select: |
+          select * from <<keyspace:baselines>>.<<table:keyvalue>> where key={seq_key};
+        verify-fields: key->seq_key, value->seq_value
+        tags:
+           name: verify
+  - name: main-read
+    tags:
+      phase: main
+      type: read
+    params:
+      ratio: 5
+      cl: <<read_cl:LOCAL_QUORUM>>
+    statements:
+      - main-select: |
+         select * from <<keyspace:baselines>>.<<table:keyvalue>> where key={rw_key};
+        tags:
+          name: main-select
+  - name: main-write
+    tags:
+      phase: main
+      type: write
+    params:
+      ratio: 5
+      cl: <<write_cl:LOCAL_QUORUM>>
+    statements:
+      - main-insert: |
+          insert into <<keyspace:baselines>>.<<table:keyvalue>>
+          (key, value) values ({rw_key}, {rw_value});
+        tags:
+           name: main-insert