As far as I know, the answer is yes, however it is unlikely that the cursor will have to probe very far to find a valid row unless your data is highly bursty. The key cache (assuming you have it enabled) will allow the query to skip unrelated rows in its search.
However I would caution against TTL'ing the world and generating a 1-to-1 ratio of writes to deletes. One approach you can try is to compound your primary key with the hour. Then the latest hour of events can be retrieved by PK lookup. If you delete older rows that are outside of the partition you're operating on, your cursor will not have to skip tombstones to find valid results. On Wed, Apr 20, 2016 at 11:37 AM, Jimmy Lin <y2k...@gmail.com> wrote: > I have a following table(using default sized tier compaction) that its > column get TTLed every hour(as we want to keep only the last 1 hour events) > > And I do > Select * from mytable where object_id = ‘xxxx’ LIMIT 1; > > And since query only interested in last/latest value, will cassandra need > to scan multiple sstables or potentially skipping tombstones data just to > get the top of the latest data? > > Or is it smart enough to know the beginning of the sstables and get the > result very efficiently? > > > CREATE TABLE mytable ( > object_id text, > created timeuuid, > my_data text > PRIMARY KEY (object_id, created) > ) WITH CLUSTERING ORDER BY (created DESC) >
