Add tests that ensures that tablet information is provided by server and it reaches the metadata in every case.
Sessions:
- Session built with keyspace
- Session with executed
USE ks
- Session with no keyspace assigned
Query types by data:
- Concrete (prepared and not):
SELECT * FROM ks.t WHERE pk = 1 AND ck = 1
- Regular prepared:
SELECT * FROM ks.t WHERE pk = ? AND ck = ?
- Concrete prepared:
SELECT * FROM ks.t WHERE pk = 1 AND ck = ?
Query types by op: SELECT, UPDATE, INSERT, DELETE, LWT_UPDATE_IF, LWT_UPDATE_IF_EXISTS, LWT_INSERT_IF_EXISTS, LWT_MANUAL_SELECT, LWT_MANUAL_UPDATE, LWT_MANUAL_INSERT, LWT_MANUAL_DELETE
LWT_MANUAL - when you force query to be LWT by enforcing consistency level to SERIAL
Query types by ks presence:
- With KS:
SELECT * FROM ks.t WHERE ...
- Without KS:
SELECT * FROM t WHERE ...
Migrated to Jira: DRIVER-248
Add tests that ensures that tablet information is provided by server and it reaches the metadata in every case.
Sessions:
USE ksQuery types by data:
SELECT * FROM ks.t WHERE pk = 1 AND ck = 1SELECT * FROM ks.t WHERE pk = ? AND ck = ?SELECT * FROM ks.t WHERE pk = 1 AND ck = ?Query types by op:
SELECT,UPDATE,INSERT,DELETE,LWT_UPDATE_IF,LWT_UPDATE_IF_EXISTS,LWT_INSERT_IF_EXISTS,LWT_MANUAL_SELECT,LWT_MANUAL_UPDATE,LWT_MANUAL_INSERT,LWT_MANUAL_DELETELWT_MANUAL- when you force query to be LWT by enforcing consistency level toSERIALQuery types by ks presence:
SELECT * FROM ks.t WHERE ...SELECT * FROM t WHERE ...Migrated to Jira: DRIVER-248