No I'm not using a seq anywhere else then the command line On Oct 13, 2016 4:40 PM, "Ben Slater (JIRA)" <j...@apache.org> wrote:
> > [ https://issues.apache.org/jira/browse/CASSANDRA-12490? > page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel& > focusedCommentId=15573119#comment-15573119 ] > > Ben Slater commented on CASSANDRA-12490: > ---------------------------------------- > > Just to check [~tjake] when you say "this also breaks validation", I > assume you mean it breaks validation when you use the sequence distribution > type, not in the case where you don't use seq()? > > > Add sequence distribution type to cassandra stress > > -------------------------------------------------- > > > > Key: CASSANDRA-12490 > > URL: https://issues.apache.org/ > jira/browse/CASSANDRA-12490 > > Project: Cassandra > > Issue Type: Improvement > > Components: Tools > > Reporter: Ben Slater > > Assignee: Ben Slater > > Priority: Minor > > Fix For: 3.10 > > > > Attachments: 12490-trunk.patch, 12490.yaml, > cqlstress-seq-example.yaml > > > > > > When using the write command, cassandra stress sequentially generates > seeds. This ensures generated values don't overlap (unless the sequence > wraps) providing more predictable number of inserted records (and > generating a base set of data without wasted writes). > > When using a yaml stress spec there is no sequenced distribution > available. It think it would be useful to have this for doing initial load > of data for testing > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) >
