Skip to content
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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

mbautin
Copy link
Contributor

@mbautin mbautin commented Jun 19, 2019

This allows testing with wide keys.

@mbautin mbautin requested a review from bmatican June 19, 2019 08:18
Copy link
Contributor

@bmatican bmatican left a 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() {
Copy link
Contributor

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;
Copy link
Contributor

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?

ameyb added a commit that referenced this pull request Aug 6, 2019
ameyb added a commit that referenced this pull request Aug 6, 2019
…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
@bmatican
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants