[
https://issues.apache.org/jira/browse/CASSANDRA-12490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15573966#comment-15573966
]
Ben Slater commented on CASSANDRA-12490:
----------------------------------------
Moving back from dev list where I think the discussion ended up by accident.
Jake said:
No I'm not using a seq anywhere else then the command line
I said:
OK, I think it’s pretty unlikely to be this change as I didn’t change the
existing code (certainly nothing near what is used by -pop) and also I just
noticed you said you had the issue in 3.9 and CASS-12490 is destined for 3.10.
Also, last time I looked, I thought stress didn’t validate returned results for
YAML specs. Did I miss something or did that get added recently? Can you add
your actual command, etc to the ticket?
Anyway, I will try to do some more digging over the weekend as I still suspect
there is something wrong (or at least unexpected) going on aside from this
change.
> 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)
