cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-9849) Paging changes to 2.1/2.2 for backward compatibilty with 3.0
Date Fri, 24 Jul 2015 07:30:05 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-9849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sylvain Lebresne resolved CASSANDRA-9849.
-----------------------------------------
       Resolution: Fixed
         Reviewer: Sylvain Lebresne
    Fix Version/s:     (was: 2.2.x)
                       (was: 2.1.x)
                   2.2.1
                   2.1.9

So, committed.

> 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.9, 2.2.1
>
>
> 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)

Mime
View raw message