I think the answer is no. There are explicit checks in Read code path to ignore anything that’s past the TTL (based on local time of the node under question).
From: Anuj Wadehra [mailto:anujw_2...@yahoo.co.in] Sent: Monday, March 21, 2016 5:19 AM To: User <user@cassandra.apache.org> Subject: Expiring Columns Hi, I want to understand how Expiring columns work in Cassandra. Query: Documentation says that once TTL of a column expires, tombstones are created/ marked when the sstable gets compacted. Is there a possibility that a query (range scan/ row query) returns expired column data just because the sstable never participated in a compaction after TTL of the column expired? For Example: 10 AM Data inserted with ttl=60 seconds 10:05 AM A query is run on inserted data 10:07 AM sstable is compacted and column is marked tombstone. Will the query return expired data in above scenario? If yes/no, why? Thanks Anuj Sent from Yahoo Mail on Android<https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2foverview.mail.yahoo.com%2fmobile%2f%3f.src%3dAndroid&data=01%7c01%7cAnubhav.Kale%40microsoft.com%7c922fa15673004fde467b08d351830013%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=%2bWLV0csy4QYjBr32XdC3nSaVD5CA%2blTbmj41mzFdcps%3d>
