[
https://issues.apache.org/jira/browse/CASSANDRA-12490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15581311#comment-15581311
]
Stefania edited comment on CASSANDRA-12490 at 10/17/16 5:53 AM:
----------------------------------------------------------------
bq. It still generates min..max as nextWithWrap() (which is called by the other
variants of next()) returns start + (next % totalCount) so it starts again from
min if it goes past max.
You're correct it does wrap, but it won't necessarily start at min, so the
documentation should clearly state this. I would also add a call to
{{setSeed()}} in one of the unit tests if the patch goes ahead.
{{inverseCumProb()}} is correct because of the wrapping.
was (Author: stefania):
bq. It still generates min..max as nextWithWrap() (which is called by the other
variants of next()) returns start + (next % totalCount) so it starts again from
min if it goes past max.
You're correct it does wrap, but it won't necessarily start at min, so the
documentation should clearly state this. I would also add a call to
{{setSeed()}} in one of the unit tests if the patch goes ahead.
{{inverseCumProb()}} is instead correct because of the wrapping.
> 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, 12490update-trunk.patch,
> 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)
