[CASSANDRA-5172] Detect (and warn) unintentional use of the cql2 thrift methods when cql3 was the intention

• Type: Improvement
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 1.2.1
• Assignee: Sylvain Lebresne
• Reporter: Sylvain Lebresne

Authors

Sylvain Lebresne

Reviewers

Jonathan Ellis

• Created: 18/Jan/13 14:56
• Updated: 16/Apr/19 09:32
• Resolved: 21/Jan/13 16:05

Description

In 1.2.0 we've separated the thrift methods for CQL2 and CQL3 (due to CASSANDRA-4734). In doing so, we've made set_cql_version a silent no-op.

However it means that the 1.1 way of querying CQL3 now silently end up calling CQL2 in 1.2.0. So I suggest that if someone calls set_cql_version, we record the version set and warn if (throw an invalid exception) if someone asks for CQL3 but later use the CQL2 methods.

Issue Links

• is duplicated by: CASSANDRA-5177 Insert on column with composite partition key fails with java.lang.IllegalStateException Cannot acces column family with composite key from CQL < 3.0.0