Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of spidaman.list@gmail.com
 designates 209.85.212.44 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=eHFrkPVaoidvZS2Y6yGlTg4Kr+h46dBdYjUqXv6iZKXNS8kF5D9rSFASxwhokL9r8I
         h+kN/qMGKa5nKBh2QRYzC0iBfK0nd2WMXFf+yVOH9esAYTsnjGsvcl4GLrfXgb9cjq0l
         r8r4VUD72LqVZREof3KmjkEBFd21RM1E0NzWA=
MIME-Version: 1.0
Date: Thu, 6 May 2010 09:17:53 -0700
Message-ID: <r2rd9d57b0c1005060917z71112bc9rb399b6c17c9ef45f@mail.gmail.com>
Subject: pagination through slices with deleted keys
From: Ian Kallen <spidaman.list@gmail.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=001485f85e40e5e29f0485ef4851

--001485f85e40e5e29f0485ef4851
Content-Type: text/plain; charset=ISO-8859-1

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

--001485f85e40e5e29f0485ef4851
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I read the DistributedDeletes and the range_ghosts FAQ entry on the wiki wh=
ich do a good job describing how difficult deletion is in an eventually con=
sistent system. But practical application strategies for dealing with it ar=
en&#39;t there (that I saw). I&#39;m wondering how folks implement paginati=
on 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 t=
here something simpler that I overlooked? I&#39;d like to be able to count =
(even if the counts are approximate) and fetch rows with the deleted ones f=
iltered 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 tombs=
tones.<br>
-Ian<br>

--001485f85e40e5e29f0485ef4851--