It's there for the same reason as the other timestamps: it lets cassandra ignore obsolete operations. So if you do a delete at time X and an insert at time Y where X < Y, the insert will not be deleted by mistake even if a node is down temporarily and gets the delete later.
-Jonathan On Mon, Aug 3, 2009 at 11:59 AM, Mark McBride<[email protected]> wrote: > If this is the case, what does the timestamp passed in to the remove > call do? I assumed you had to have it match up with a specific > version... > > On Mon, Aug 3, 2009 at 9:53 AM, <[email protected]> wrote: >> I always thought cassandra had free multiple versions and we needed to >> manually delete the older versions >> >> On Mon, Aug 3, 2009 at 8:56 AM, Jonathan Ellis <[email protected]> wrote: >>> >>> On Mon, Aug 3, 2009 at 10:49 AM, Jun Rao<[email protected]> wrote: >>> > Ivan, >>> > >>> > The original cassandra keeps multiple versions of the column data. >>> >>> No, it didn't. (It had versioning-related bugs but multiple versions >>> a la Bigtable was never part of the design.) >>> >>> -Jonathan >> >> >> >> -- >> Bidegg worlds best auction site >> http://bidegg.com >> >
