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

more docs

Browse Source
This commit is contained in:
Jonathan Shook
2020-04-07 16:16:03 -05:00
parent 34ab6832c9
commit 10d5ac9732
2 changed files with 9 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
engine-docs/docs/slack_invite.md Normal file
View File

@@ -0,0 +1 @@
[Slack Invite](https://docs.google.com/forms/d/e/1FAIpQLSdUOJ8iAPqyxsLfh1nBBsKShI53RAeuzYW4bKExmRMWjj4ufQ/viewform)

8
engine-docs/src/main/resources/docs-for-nb/designing_workloads/10_named_scenarios.md
View File

@@ -203,3 +203,11 @@ $
Ultimately, it is up to the scenario designer when to lock parameters for users. The built-in workloads offer some
examples on how to set these parameters so that the right value are locked in place without bother the user, but some
values are made very clear in how they should be set. Please look at these examples for inspiration when you need.
## Enforcing UNDEF
If you want to ensure that any parameter in a named scenario template remains unset in the generated scenario script,
you can assign it a value of UNDEF. The locking behaviors described above apply to this one as well. Thus, for schema
commands which rely on the default sequence length (which is based on the number of active statements), you can set
cycles==UNDEF to ensure that when a user passes a cycles parameter the schema phase doesn't break with too many cycles.