cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "T Jake Luciani (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8608) Fix cassandra-stress bug introduced by 7964, and cleanup related code a little
Date Fri, 16 Jan 2015 15:59:34 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-8608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14280438#comment-14280438
] 

T Jake Luciani commented on CASSANDRA-8608:
-------------------------------------------

Well it seems to now use more than a single node but it isn't respecting the limit per batch.
You can test it easily with the profile from CASSANDRA-8632



> Fix cassandra-stress bug introduced by 7964, and cleanup related code a little
> ------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-8608
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8608
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Benedict
>            Assignee: Benedict
>
> 7964 had a very basic mistake present when wiring up writes - the "limit" was not reset,
so only the first row would be returned (the fact _ANY_ row was returned was itself sort-of
a bug in this scenario, and I've changed this also). At the same time I've changed the definition
of limit to lastRow so that the related functionality is clearer and more obviously correct.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message