cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3130) CQL queries should alow talbe names to be qualified by keyspace
Date Fri, 02 Sep 2011 23:40:09 GMT


Eric Evans commented on CASSANDRA-3130:

I disagree, all of the Good reasons for making that change to the RPC back then, hold true
today whether you're talking about RPC or CQL.

The "keyspace" is equivalent to "database" in other systems that use SQL, it's the application-specific
namespace.  In which of these systems are you able to qualify a table with the database name
like this?

> CQL queries should alow talbe names to be qualified by keyspace
> ---------------------------------------------------------------
>                 Key: CASSANDRA-3130
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Edward Capriolo
>            Priority: Minor
>             Fix For: 1.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.
For more information on JIRA, see:


View raw message