cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Blake Eggleston (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10354) Invalid paging with DISTINCT on static and IN
Date Fri, 18 Sep 2015 20:35:04 GMT

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

Blake Eggleston commented on CASSANDRA-10354:
---------------------------------------------

I'm still getting sporadic failures with {{upgrade_tests/paging_test.py:TestPagingData.static_columns_paging_test}}
(see output [here|https://gist.github.com/bdeggleston/d7c8de409ff598ea606d]). Adding a bunch
of debug logging to the upgraded nodes produces this: https://gist.github.com/bdeggleston/c67f91d34394520afec6,
which shows that the first response returns all the requested rows. The upgraded node then
sends a second read request with an empty names filter, and receives the first 5 rows of that
partition, then sends another 3.

> Invalid paging with DISTINCT on static and IN
> ---------------------------------------------
>
>                 Key: CASSANDRA-10354
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10354
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>             Fix For: 3.0.0 rc1
>
>
> Basically, the test from CASSANDRA-10352 happens to fail on 3.0, but not for the reason
in CASSANDRA-10352 but rather because it incorrectly return duplicate results. This is also
the reason for the failure of {{upgrade_tests/paging_test.py:TestPagingData.static_columns_paging_test}}
once that test doesn't run into CASSANDRA-10352 (which it currently does).



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

Mime
View raw message