improve parser error messages to include op template name

This commit is contained in:
Jonathan Shook
2022-06-30 16:11:17 -05:00
parent 1371bee288
commit 2e4776f893
52 changed files with 683 additions and 1100 deletions

View File

@@ -1,3 +1,5 @@
min_version: "4.17.15"
description: |
A workload with only text keys and text values. This is based on the CQL keyvalue workloads as found
in cql-keyvalue2.yaml.
@@ -6,11 +8,12 @@ scenarios:
default:
schema: run driver=dynamodb tags==block:schema threads==1 cycles==UNDEF
rampup: run driver=dynamodb tags==block:rampup cycles===TEMPLATE(rampup-cycles,10000000) threads=auto
main: run driver=dynamodb tags=='block:main.*' cycles===TEMPLATE(main-cycles,10000000) threads=auto
main: run driver=dynamodb tags=="block:main.*" cycles===TEMPLATE(main-cycles,10000000) threads=auto
read: run driver=dynamodb tags==block:main-read cycles===TEMPLATE(main-cycles,10000000) threads=auto
write: run driver=dynamodb tags==block:main-write cycles===TEMPLATE(main-cycles,10000000) threads=auto
delete:
table: run driver=dynamodb tags==block:delete threads==1 cycles==UNDEF
main-read: run driver=dynamodb tags==block:main-read cycles===TEMPLATE(main-cycles,10000000) threads=auto
main-write: run driver=dynamodb tags==block:main-write cycles===TEMPLATE(main-cycles,10000000) threads=auto
bindings:
seq_key: Mod(<<keycount:1000000000>>); ToString() -> String

View File

@@ -1,3 +1,5 @@
min_version: "4.17.15"
description: |
Run a read/write workload against DynamoDB with varying field sizes and query patterns
@@ -5,7 +7,7 @@ scenarios:
schema: run driver=dynamodb tags=block:schema region=us-east-1
rampup: run driver=dynamodb tags=block:rampup region=us-east-1
read: run driver=dynamodb tags=block:read region=us-east-1
main: run driver=dynamodb tags=block:main region=us-east-1
main: run driver=dynamodb tags=block:"main.*" region=us-east-1
read01: run driver=dynamodb tags='name:.*main-read-01' region=us-east-1
delete:
table: run driver=dynamodb tags==block:delete threads==1 cycles==UNDEF
@@ -39,9 +41,7 @@ params:
instrument: true
blocks:
- name: schema
tags:
phase: schema
schema:
ops:
create-table:
CreateTable: TEMPLATE(table,tabular)
@@ -54,10 +54,8 @@ blocks:
BillingMode: PROVISIONED
ReadCapacityUnits: "TEMPLATE(rcus,40000)"
WriteCapacityUnits: "TEMPLATE(wcus,40000)"
# BillingMode: PAY_PER_REQUEST
- name: rampup
tags:
phase: rampup
# BillingMode: PAY_PER_REQUEST
rampup:
ops:
put-items:
PutItem: TEMPLATE(table,tabular)
@@ -74,9 +72,7 @@ blocks:
"data6": "{data6}",
"data7": "{data7}"
}
- name: read
tags:
phase: read
read:
params:
ratio: 1
ops:
@@ -85,7 +81,7 @@ blocks:
key:
part: "{part_read}"
clust: "{clust_read}"
- name: main
main:
ops:
write-all:
params:
@@ -176,9 +172,7 @@ blocks:
projection: data0, data1, data2, data3, data4, data5, data6, data7
Limit: "{limit}"
- name: delete
tags:
phase: delete
delete:
ops:
delete-table:
DeleteTable: TEMPLATE(table,tabular)
DeleteTable: TEMPLATE(table,tabular)

View File

@@ -1,4 +1,5 @@
# nb -v run driver=cql yaml=cql-iot tags=phase:schema host=dsehost
min_version: "4.17.15"
description: |
This workload emulates a time-series data model and access patterns. This is based on the
cql-timeseries2 workload. This workload does not do full temporal range scans. Like
@@ -87,4 +88,4 @@ blocks:
delete:
ops:
delete-table:
DeleteTable: TEMPLATE(table,timeseries)
DeleteTable: TEMPLATE(table,timeseries)