cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8326) Cqlsh cannot connect in trunk
Date Tue, 18 Nov 2014 18:03:34 GMT


Aleksey Yeschenko commented on CASSANDRA-8326:

Also, for the record, in this particular case I was wrong to push that ninja-commit, despite
the fact that all of those schema tables will be disappearing entirely in 3.0.

Aside from cqlsh, CqlRecordWriter was for some reason still taking its columns info from key_aliases
and column_aliases. All using Thrift, too. Will fix that separately this time instead of reverting
the patch, though.

Sorry about all that.

> Cqlsh cannot connect in trunk
> -----------------------------
>                 Key: CASSANDRA-8326
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Philip Thompson
>            Assignee: Tyler Hobbs
>             Fix For: 3.0
> Cqlsh errors with {code}Unable to connect to any servers', {'': KeyError('column_aliases',)}{code}.
To fix, we need to pull in a newer version of the python driver that doesn't assume certain
metadata exists. This was broken by the cassandra commit {{cbbc1191ce1656a92354a4fa3859626cb10083e5}}.
A fix should be in version 2.1.3 of the driver.

This message was sent by Atlassian JIRA

View raw message