Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 32349 invoked from network); 23 Mar 2010 14:10:39 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 23 Mar 2010 14:10:39 -0000 Received: (qmail 70914 invoked by uid 500); 23 Mar 2010 14:10:39 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 70905 invoked by uid 500); 23 Mar 2010 14:10:38 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 70897 invoked by uid 99); 23 Mar 2010 14:10:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Mar 2010 14:10:38 +0000 X-ASF-Spam-Status: No, hits=4.4 required=10.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of zyxt001@gmail.com designates 209.85.222.190 as permitted sender) Received: from [209.85.222.190] (HELO mail-pz0-f190.google.com) (209.85.222.190) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Mar 2010 14:10:31 +0000 Received: by pzk28 with SMTP id 28so47585pzk.11 for ; Tue, 23 Mar 2010 07:10:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=d6C9NDvVbtwLC4qk8q94fmeNZ2vu0jdPDmNPMinwiw0=; b=NW7VGo8F8bth5Edfbt2DHh+1MYQtAAX3RAJqEcHxbsXgkdWIrsrmT4qfGpzZoYgzFE Bdy1ikf3oMm6ReoOxQbkNz0biMdafAUy5D1YMbEQC8Jp2yFz8LVaNJfl1TIO8AOWvedr WIdvEq75PUiybv4OKvzWWmcxYhHSdEVpeKhiA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=pg4jnLa490uoeXKa6A8fIA9UuQy/0c3z5jblSGFjgctDx864kVFhFKrk/ihh46S9JK sbb6LklYebwyWmfQ+wNB6J35vG5RZBXw/npXWivo9f54RbMs5y7EPuBc6+RcJZHAWia+ DO+zTUvM/Ho4oz7VwC0HlaIGa/IjASK5ZUcS8= MIME-Version: 1.0 Received: by 10.140.192.8 with HTTP; Tue, 23 Mar 2010 06:56:27 -0700 (PDT) In-Reply-To: <42F3BE57026C6E49B09E267EEF639D5605122B9C@ms-dt01thalia.tsn.tno.nl> References: <42F3BE57026C6E49B09E267EEF639D5605122B9C@ms-dt01thalia.tsn.tno.nl> Date: Tue, 23 Mar 2010 21:56:27 +0800 Received: by 10.141.188.24 with SMTP id q24mr56025rvp.0.1269352587640; Tue, 23 Mar 2010 06:56:27 -0700 (PDT) Message-ID: Subject: Re: Timestamp for versioning? From: =?GB2312?B?1cXT7g==?= To: user@cassandra.apache.org Cc: "Waaij, B.D. (Bram) van der" Content-Type: multipart/alternative; boundary=000e0cd17ed414be8f0482782ebc X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd17ed414be8f0482782ebc Content-Type: text/plain; charset=ISO-8859-1 HBase supports the version through the timestamp,but Cassandra not. 2010/3/23 Waaij, B.D. (Bram) van der > Hi there, > > Is there already support for doing something with the timestamp? I would > like to use it as a versioning mechanism of the value belonging to a certain > key. When i store a column with the same key, different value and different > timestamp, would i still be able to retrieve both versions? > > Looking at the API I can not find such method, but perhaps I am missing > something as I am new to cassandra. > > Best regards, > Bram > > This e-mail and its contents are subject to the DISCLAIMER at http://www.tno.nl/disclaimer/email.html > > --000e0cd17ed414be8f0482782ebc Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable HBase supports the version through the timestamp,but Cassandra not.

=
2010/3/23 Waaij, B.D. (Bram) van der <bram.vanderwaaij@tn= o.nl>

Hi there,

Is there already support for doing somet= hing with the timestamp? I would like to use it as a versioning mechanism o= f the value belonging to a certain key. When i store a column with the same= key, different value and different timestamp, would i still be able to ret= rieve both versions?

Looking at the API I can not find such m= ethod, but perhaps I am missing something as I am new to cassandra.

Best regards,
Bram

This e-mail and its contents are subject to the DISCLAIMER at http://www.t=
no.nl/disclaimer/email.html

--000e0cd17ed414be8f0482782ebc--