[ https://issues.apache.org/jira/browse/CASSANDRA-3130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13130059#comment-13130059 ]
Pavel Yaskevich commented on CASSANDRA-3130: -------------------------------------------- I guess I can clone ClientState to isolate SELECT with set keyspace name. > CQL queries should alow talbe names to be qualified by keyspace > --------------------------------------------------------------- > > Key: CASSANDRA-3130 > URL: https://issues.apache.org/jira/browse/CASSANDRA-3130 > 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 keyspace1.cf; > select * from keyspace2.cf; > {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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira