[CASSANDRA-10145] Change protocol to allow sending key space independent of query string

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.0-alpha1, 4.0
• Labels: protocolv5
• Impacts: Clients
• Assignee: Sandeep Tamhankar
• Reporter: Vishy Kasar

Authors

Sandeep Tamhankar

Reviewers

Robert Stupp

• Created: 20/Aug/15 20:08
• Updated: 15/May/20 08:01
• Resolved: 12/Apr/17 18:58

Description

Currently keyspace is either embedded in the query string or set through "use keyspace" on a connection by client driver.

There are practical use cases where client user has query and keyspace independently. In order for that scenario to work, they will have to create one client session per keyspace or have to resort to some string replace hackery.

It will be nice if protocol allowed sending keyspace separately from the query.

Issue Links

• is duplicated by: CASSANDRA-12574 Make connections state-less; do not bind a keyspace to the connection