This is a great question, and you (using) provided all the information we need to answer!
Your first query is a point search (since you specify both clustering keys). The second is a slice.
If we look at the trail, the obvious difference is in your track:
Skipped 8/9 non-slice-intersecting sstables, included 5 due to tombstones
, . , , , , , memtable/sstables - , , sstables.
, - :
/**
* Do a read by querying the memtable(s) first, and then each relevant sstables sequentially by order of the sstable
* max timestamp.
*
* This is used for names query in the hope of only having to query the 1 or 2 most recent query and then knowing nothing
* more recent could be in the older sstables (which we can only guarantee if we know exactly which row we queries, and if
* no collection or counters are included).
* This method assumes the filter is a {@code ClusteringIndexNamesFilter}.
*/
:
, , () . , 8 sstables, , , STCS TWCS - LCS, , ~ 5 sstables, ( ) .
, memtable, , memtable. , , , .
- , ( , ). , FAR , - - / ( ) c1 = '2017-09-05T16:09:00.222Z'
: :
Defragmenting requested data
, STCS sstables, , . STCS, sstables, LCS.