I would guess Jake replied to the JIRA message that was sent to commits@
expected the reply to end up going back to the ticket (which happens if you
reply to something JIRA sends directly to you because you watched the ticket),
but instead went to dev@ because the emails sent to commits@ from JIRA have a
reply to of dev@, not back to the ticket.
> On Oct 13, 2016, at 7:40 PM, Ben Slater <ben.sla...@instaclustr.com> wrote:
> 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
> 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.
> (BTW - I noticed you moved the discussion from JIRA to the dev list. What’s
> the etiquette there?)
> On Fri, 14 Oct 2016 at 09:02 Jake Luciani <jak...@gmail.com> wrote:
>> 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?
>>> 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
>>> 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/
>>>> 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,
>>>> 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
>>> of data for testing
>>> This message was sent by Atlassian JIRA
> Ben Slater
> Chief Product Officer
> Instaclustr: Cassandra + Spark - Managed | Consulting | Support
> +61 437 929 798