[
https://issues.apache.org/jira/browse/CASSANDRA-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14318439#comment-14318439
]
Tyler Hobbs commented on CASSANDRA-8767:
----------------------------------------
In the meantime, you should be able to work around this by disabling paging (at
least for this query) through the driver. Neither cqlsh (in Cassandra 2.0) nor
the old cql python library have paging, which is why you're not seeing the
problem there.
You can either disable paging [for the whole
session|http://datastax.github.io/python-driver/api/cassandra/cluster.html#cassandra.cluster.Session.default_fetch_size]
or for [the specific
query|http://datastax.github.io/python-driver/api/cassandra/query.html#cassandra.query.Statement.fetch_size].
> "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: describe-table.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)
