Overview
Choose the right MTS surface and bounded serving model.
Reference
Query syntax quick map
| Surface | Primary use | Parameter style | Bounded-read rule |
|---|---|---|---|
| CQL native protocol | Cassandra-compatible keyspace/table access, prepared statements, CQL batches, MTS extensions where enabled. | Native driver markers, usually ? in prepared statements. | Complete primary key, admitted clustering/range read, or queryable access path. |
| MTS SQL mode | SQL-shaped OLTP statements over the same native protocol endpoint. | $1, $2, ... in prepared SQL text. | Same bounded planning contract; SQL syntax does not imply scan permission. |
| REST API | HTTP adapter over public MTS execution, prepared, data helper, explain/advice, catalog, routing, cluster, import/export surfaces. | JSON typed values and request bodies. | Statement and helper requests must still be admitted by the MTS planner. |
| DynamoDB-compatible HTTP | AWS JSON protocol compatibility for item, query, scan, batch, transaction, table admin, stream, backup/import/export operations. | DynamoDB ExpressionAttributeValues and JSON attribute values. | Query must include hash-key equality; Scan is compatibility-oriented and should be treated carefully on OLTP paths. |
LIMIT, REST page size, DynamoDB Limit, and vector topk cap result output or evaluation windows. They do not by themselves prove the engine can find the first page without unsafe work.