In the spirit of
CASSANDRA-4851 and to bring CQL to parity with Thrift, it is important to support reading several distinct CQL rows from a given partition using a distinct set of "coordinates" for these rows within the partition. CASSANDRA-4851 introduced a range scan over the multi-dimensional space of clustering keys. We also need to support a "multi-get" of CQL rows, potentially using the "IN" keyword to define a set of clustering keys to fetch at once.
(reusing the same example:)
Consider the following table:
with the following data:
We can fetch a single row or a range of rows, but not a set of them:
Supporting this syntax would return:
Being able to fetch these two CQL rows in a single read is important to maintain partition-level isolation.