You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2015/07/20 14:45:04 UTC
[jira] [Created] (CASSANDRA-9849) Paging changes to 2.1/2.2 for
backward compatibilty with 3.0
Sylvain Lebresne created CASSANDRA-9849:
-------------------------------------------
Summary: Paging changes to 2.1/2.2 for backward compatibilty with 3.0
Key: CASSANDRA-9849
URL: https://issues.apache.org/jira/browse/CASSANDRA-9849
Project: Cassandra
Issue Type: Bug
Reporter: Sylvain Lebresne
Assignee: Tyler Hobbs
Fix For: 2.1.x, 2.2.x
Quoting [~thobbs] from CASSANDRA-9704:
{quote}
I forgot to attach a patch for the required 2.1/2.2 changes as well. Basically, when paging in 2.x, our check to see if a new page contains the same row that the previous page ended on looks for an exact cell name match. This is fine in 2.x because we will return partial rows at the end of the page (just the row marker cell). However, in 3.0, we always return full rows. While we could make some very hacky changes to 3.0 to enable returning a partial row at the end of the page, this seems like the cleanest solution.
{quote}
Tyler's patch is [there|https://github.com/thobbs/cassandra/tree/CASSANDRA-9704-2.1-forward-compat]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)