[
https://issues.apache.org/jira/browse/CASSANDRA-8608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14280451#comment-14280451
]
T Jake Luciani commented on CASSANDRA-8608:
-------------------------------------------
ok.
If I raise the limit 10x I start getting this error...
{code}
Exception in thread "Thread-64" java.lang.AssertionError
at
org.apache.cassandra.stress.generate.PartitionIterator$MultiRowIterator.advance(PartitionIterator.java:446)
at
org.apache.cassandra.stress.generate.PartitionIterator$MultiRowIterator.seek(PartitionIterator.java:351)
at
org.apache.cassandra.stress.generate.PartitionIterator$MultiRowIterator.reset(PartitionIterator.java:259)
at
org.apache.cassandra.stress.generate.PartitionIterator.reset(PartitionIterator.java:101)
at org.apache.cassandra.stress.Operation.ready(Operation.java:110)
at
org.apache.cassandra.stress.StressAction$Consumer.run(StressAction.java:288)
{code}
> 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)
