cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8767) "Added column does not sort as the last column" when using new python driver
Date Wed, 18 Feb 2015 17:38:11 GMT


Tyler Hobbs commented on CASSANDRA-8767:

I came up with an [identical patch|]
yesterday.  It does fix the problem and doesn't break any paging tests.  I also pushed my
[dtest test case|].

I'm a little worried that there may be other, similarly subtle breakage around how reversed
CFs are handled, but since we haven't seen them yet and this fixes a known problem, +1 and

> "Added column does not sort as the last column" when using new python driver
> ----------------------------------------------------------------------------
>                 Key: CASSANDRA-8767
>                 URL:
>             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,
> 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
> Where buffer and idkey are integer primary keys, and id is the clustering key (ordered
> 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

View raw message