[ https://issues.apache.org/jira/browse/CASSANDRA-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14325661#comment-14325661 ]
Sylvain Lebresne commented on CASSANDRA-8767: --------------------------------------------- While serializing the {{reversed}} flag could maybe make sense (I say maybe because in practice we are serializing cells in (non-reversed) comparator order, so we'd have to handle deserialization specially if we were doing that, which may not be an improvement (but I can agree the way we handle reversed queries is weird)), I don't think it's practical option. But as the CF on which this happen in the paging code is a shallow clone in the first place, and pager knows if it's a reversed query or not, I think we can just clone with the proper insertion order flag. Attaching trivial patch to show what I mean (untested and without tests, we should push the test you've been using as dtest). > "Added column does not sort as the last column" when using new python driver > ---------------------------------------------------------------------------- > > Key: CASSANDRA-8767 > URL: https://issues.apache.org/jira/browse/CASSANDRA-8767 > Project: Cassandra > Issue Type: Bug > Components: Core, Drivers (now out of tree) > Environment: Cassandra 2.0.10, python-driver 2.1.3 > Reporter: Russ Garrett > Assignee: Tyler Hobbs > Fix For: 2.0.13 > > Attachments: 8767-debug-logging.txt, 8767.patch, describe-table.txt, > exception-with-logging.txt, exception.txt > > > We've just upgraded one of our python apps from using the old cql library to > the new python-driver. When running one particular query, it produces the > attached assertion error in Cassandra. The query is: > bq. SELECT buffer, id, type, json FROM events WHERE buffer = %(bid)s AND > idkey = %(idkey)s ORDER BY id ASC > Where buffer and idkey are integer primary keys, and id is the clustering key > (ordered asc). > This query, with identical parameters, does not cause this error using the > old cql python library, or with the cqlsh client.. -- This message was sent by Atlassian JIRA (v6.3.4#6332)