cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carl Yeksigian (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5378) Fat Client: No longer works in 1.2
Date Fri, 05 Apr 2013 18:51:17 GMT


Carl Yeksigian commented on CASSANDRA-5378:

If we don't have that, we won't be able to validate a query against the row key.

That is, if the schema is:
CREATE COLUMNFAMILY standard1 ( id ascii PRIMARY KEY , name ascii , value blob ) ;
SELECT * FROM standard1 WHERE id='abc';

That select statement will not be validated, as no column is indexed, but the row key is.
It'll throw the "No indexed columns present in by-columns clause with Equal operator" exception.
> Fat Client: No longer works in 1.2
> ----------------------------------
>                 Key: CASSANDRA-5378
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.2.0
>            Reporter: Carl Yeksigian
>            Assignee: Carl Yeksigian
>              Labels: client
>             Fix For: 1.2.4
>         Attachments: 5378-1.2.txt, 5378.txt, 5378-v2.txt
> The current client only example doesn't compile. After doing some updates, the fat client
still won't work, mainly because the schema is not being pushed to the fat client.
> I've made changes to the client to support CQL3 commands, to the ServiceManager to wait
until a migration has completed before starting the client, and to the MigrationManager to
not try to pull schemas from a fat client.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message