[
https://issues.apache.org/jira/browse/CASSANDRA-4136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251619#comment-13251619
]
Jonathan Ellis commented on CASSANDRA-4136:
-------------------------------------------
With this and the 3883 patches I get
{noformat}
$ cat /tmp/word_count5/part-r-00000
0 250
1 250
2 250
3 250
word1 2002
word2 1
{noformat}
which is the expected result.
+1
> get_paged_slices doesn't reset startColumn after first row
> ----------------------------------------------------------
>
> Key: CASSANDRA-4136
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4136
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.0
> Reporter: Jonathan Ellis
> Assignee: Sylvain Lebresne
> Priority: Critical
> Fix For: 1.1.0
>
> Attachments: 4136.txt
>
>
> As an example, consider the WordCount example (see CASSANDRA-3883).
> WordCountSetup inserts 1000 rows, each with three columns: text3, text4,
> int1. (Some other miscellaneous columns are inserted in a few rows, but we
> can ignore them here.)
> Paging through with get_paged_slice calls with a count of 99, CFRecordReader
> will first retrieve 33 rows, the last of which we will call K. Then it will
> attempt to fetch 99 more columns, starting with row K column text4.
> The bug is that it will only fetch text4 for *each* subsequent row K+i,
> instead of returning (K, text4), (K+1, int1), (K+1, int3), (K+1, text4), etc.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
