cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3130) CQL queries should alow talbe names to be qualified by keyspace
Date Tue, 18 Oct 2011 22:01:12 GMT


Jonathan Ellis commented on CASSANDRA-3130:

IMO the "right" fix is to make things like hasColumnFamilyAccess take a keyspace parameter
(maybe just as an overload to keep the common case simple)
> CQL queries should alow talbe names to be qualified by keyspace
> ---------------------------------------------------------------
>                 Key: CASSANDRA-3130
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Edward Capriolo
>            Assignee: Pavel Yaskevich
>            Priority: Minor
>             Fix For: 1.0.1
> While the 0.6.X api was "ugly" in terms of method signatures, it did allow you to use
the same client to query multiple keyspaces without having to call set_keyspace(String). I
totally dislike set_keyspace but I know the thrift API is definitely not changing.
> The following command sequence is three RPC operations.
> {noformat}
> select * from cf;
> use otherkeyspace;
> select * from othercf;
> {noformat}
> CQL should allow us to do:
> {noformat}
> select * from;
> select * from;
> {noformat}
> This will make the connection pool management on the client much easier.

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


View raw message