-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow specifying the number of range keys in CassandraTransactionalKeyValue workload #16
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor comments
} | ||
|
||
|
||
private String getCommasAndRangeKeys() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: add a comment that this returns a string with a , at the start, I almost missed that...
@@ -162,4 +162,7 @@ | |||
|
|||
// The number of client connections to establish to each host in the YugaByte DB cluster. | |||
public int concurrentClients = 4; | |||
|
|||
// Number of range keys to include in the primary key. | |||
public int numRangeKeys = -1; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
any reason to default this to -1 but the static defaults in the app to 0?
…18) * Adding new workload type for Event data timeseries for IoT use-cases * -Added device id, configurable number of devices and event types and Random payload * Updated minor changes for syntax and comments for variables used based on PR review #16 * Updated README and Commandline params * Removed commented variables
Was just talking to @rao-vasireddy , that it might be useful to also have a feature for the non-txn workloads, where we can specify the number of non-key columns, to see what the perf implications would be in running a 10 column table vs a 20 column table. |
This allows testing with wide keys.