Quick question: Cassandra documentation explains implementation of deletes (using tombstones) quite well. But what I was not quite sure about was what actual effects of existing tombstones might have on doing range queries that would include those tombstones. That is: for a use case where new entries are always added at the end (like using time uuid as key, or just simple timestamp), but read and deleted from head (oldest entry), and range query always use minimal key. When accessing rows, does Cassandra then have to filter out all deleted (tombstone) entries from range?
-+ Tatu +-
