I read the DistributedDeletes and the range_ghosts FAQ entry on the wiki
which do a good job describing how difficult deletion is in an eventually
consistent system. But practical application strategies for dealing with it
aren't there (that I saw). I'm wondering how folks implement pagination in
their applications; if you want to render N results in an application, is
the only solution to over-fetch and filter out the tombstones? Or is there
something simpler that I overlooked? I'd like to be able to count (even if
the counts are approximate) and fetch rows with the deleted ones filtered
out (without waiting for the GCGraceSeconds interval + compaction) but from
what I see so far, the burden is on the app to deal with the tombstones.
-Ian
