family indexes. Most applications can be designed with a data model that supports ordered queries as slices over a set of columns rather than range scans over a set of rows. Using an ordered partitioner is row key (a row that contains no columns). These deleted keys can show up in results of get_range_slices() calls. If your client application performs range queries on rows, you may want to have if filter data when switching partioners.) -g , --keys-per-call Number of keys to get_range_slices or multiget per call. Default is 1000. -r, --random Only used for reads. By default, stress will