[
https://issues.apache.org/jira/browse/CASSANDRA-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14324503#comment-14324503
]
Tyler Hobbs commented on CASSANDRA-8767:
----------------------------------------
Thanks, that provides some insight. It's adding the cell (<int-value>, "json")
after (<int-value>, "type") with the same value for <int-value>. The
comparator for this schema includes a UTF8Type component at the end for the
column name (and it's always in normal sorting order), so "json" should come
before "type".
I was able to reproduce this with a multi-node cluster, so this is happening
somewhere that the single-node path doesn't trigger.
> "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, 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)
