IntenseFinance/nosqlbench
3
0
Fork 0
mirror of https://github.com/nosqlbench/nosqlbench.git synced 2025-02-25 18:55:28 -06:00
Code Issues Packages Projects Releases Wiki Activity

Use the correct keyspace in graphql kv and fix descriptions

Browse Source
This commit is contained in:
Doug Wettlaufer 2021-04-26 12:49:45 -05:00
parent 871350d42a
commit 7ff1e3db3a
4 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
driver-http/src/main/resources/activities/baselines/http-rest-tabular.yaml
View File

@ -1,6 +1,6 @@
# nb -v http-rest-tabular rampup-cycles=1E6 main-cycles=1E9 stargate_host=my_stargate_host host=my_stargate_host auth_token=$AUTH_TOKEN # nb -v http-rest-tabular rampup-cycles=1E6 main-cycles=1E9 stargate_host=my_stargate_host host=my_stargate_host auth_token=$AUTH_TOKEN
description: | description: |
This workload emulates a time-series data model and access patterns. This workload emulates a tabular workload with partitions, clusters, and data fields.
This should be identical to the cql variant except for: This should be identical to the cql variant except for:
- We need to URLEncode the `data` and `data_write` bindings because newlines can't be sent in REST calls. - We need to URLEncode the `data` and `data_write` bindings because newlines can't be sent in REST calls.
- There is no instrumentation with the http driver. - There is no instrumentation with the http driver.

2
driver-http/src/main/resources/activities/graphql-cql-first/http-graphql-cql-keyvalue.yaml
View File

@ -37,7 +37,7 @@ blocks:
X-Cassandra-Token: "<<auth_token:my_auth_token>>" X-Cassandra-Token: "<<auth_token:my_auth_token>>"
Content-Type: "application/json" Content-Type: "application/json"
body: | body: |
{"query":"mutation {\n createKeyspace(name:\"<<keyspace:gqlcf_tabular>>\", replicas: <<rf:1>>, ifNotExists: true)\n}"} {"query":"mutation {\n createKeyspace(name:\"<<keyspace:gqlcf_keyvalue>>\", replicas: <<rf:1>>, ifNotExists: true)\n}"}
tags: tags:
name: create-keyspace name: create-keyspace
- create-table: POST <<protocol:http>>://{weighted_hosts}:<<stargate_port:8080>><<path_prefix:>>/graphql-schema - create-table: POST <<protocol:http>>://{weighted_hosts}:<<stargate_port:8080>><<path_prefix:>>/graphql-schema

2
driver-http/src/main/resources/activities/graphql-cql-first/http-graphql-cql-tabular.yaml
View File

@ -1,6 +1,6 @@
# nb -v http-graphql-cql-tabular rampup-cycles=1E6 main-cycles=1E9 stargate_host=my_stargate_host host=my_stargate_host auth_token=$AUTH_TOKEN # nb -v http-graphql-cql-tabular rampup-cycles=1E6 main-cycles=1E9 stargate_host=my_stargate_host host=my_stargate_host auth_token=$AUTH_TOKEN
description: | description: |
This workload emulates a time-series data model and access patterns. This workload emulates a tabular workload with partitions, clusters, and data fields.
This should be identical to the cql variant except for: This should be identical to the cql variant except for:
- We need to URLEncode the `data` and `data_write` bindings because newlines can't be sent in REST calls. - We need to URLEncode the `data` and `data_write` bindings because newlines can't be sent in REST calls.
- There is no instrumentation with the http driver. - There is no instrumentation with the http driver.

2
driver-http/src/main/resources/activities/graphql-schema-first/http-graphql-tabular.yaml
View File

@ -6,7 +6,7 @@
# - rest uses limit as it queries only by a single primary key, we can not map this to GQL (also should data be clustering key) # - rest uses limit as it queries only by a single primary key, we can not map this to GQL (also should data be clustering key)
description: | description: |
This workload emulates a time-series data model and access patterns. This workload emulates a tabular workload with partitions, clusters, and data fields.
This should be identical to the cql variant except for: This should be identical to the cql variant except for:
- We need to URLEncode the `data` and `data_write` bindings because newlines can't be sent in REST calls. - We need to URLEncode the `data` and `data_write` bindings because newlines can't be sent in REST calls.
- Schema creation GraphQL first, we don't use cql and thus can only create schema with limited options. - Schema creation GraphQL first, we don't use cql and thus can only create schema with limited options.