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 jbellis@gmail.com designates
 209.85.210.44 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=XDz7uUS5GRNpRyhmeVwJ1YhtWsZVPsPXTlrNUIERqRhg2QldhE6soDWf5uUzN9yifF
         Iuh94GgqluwdkHUsxBLbqqcMmHCpOMGLtddQ9E5sOUZWZILW+pbdNNaNQSSbSkGqnY9k
         SNYYSOOJzyudEzakcZ0dn4ktvTCF4KSm9GGQM=
MIME-Version: 1.0
In-Reply-To: <AANLkTi=kOa2T=m0i0C_Krr6p59NJJU_GJ_VmG0KZC6ap@mail.gmail.com>
References: <AANLkTi=gEqCcWi3GZNJOuJO1yutXguzTjgaMcep0mSyj@mail.gmail.com>
 <AANLkTi=kOa2T=m0i0C_Krr6p59NJJU_GJ_VmG0KZC6ap@mail.gmail.com>
From: Jonathan Ellis <jbellis@gmail.com>
Date: Sat, 5 Feb 2011 22:51:00 -0600
Message-ID: <AANLkTin_PHt1nJomAQXeiOyc=fq1L_wPLauq-AbnRUt9@mail.gmail.com>
Subject: Re: revisioned data
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Using supercolumns to contain versions is reasonable, as long as the
number of versions is not too large.

On Sat, Feb 5, 2011 at 4:38 PM, Victor Kabdebon
<victor.kabdebon@gmail.com> wrote:
> Hello Raj,
>
> No it actually doesn't make sense from the point of view of Cassandra;
> OrderingPartioner preserves the order of the keys. The Ordering will be d=
one
> according to the supercolumn name. In that case you can set the ordering
> with compare_super_with (sorry I don't remember exactly the new term in
> Cassandra, but that's the idea). The compare_with will order your columns
> inside your supercolumn.
>
> However, and I think that many will agree here, tend to avoid SuperColumn=
.
> Rather than using SuperColumns try to think like that :
>
> CF1 : "ObjectStore"
> Key :ID (long)
> Columns : {
> =A0=A0=A0 name
> =A0=A0=A0 other fields
> =A0=A0=A0 update time (long [date])
> =A0=A0=A0 ...}
>
> CF2 : "ObjectOrder"
> Key : "myorderedobjects
> Column:{
> =A0=A0 { name : identifier that can be sorted
> =A0=A0 value :ObjectID},
> =A0=A0 ...
> }
>
> Best regards,
> Victor Kabdebon,
> http://www.voxnucleus.fr
>
> 2011/2/5 Raj Bakhru <rbakhru@gmail.com>
>>
>> Hi all -
>>
>> We're new to Cassandra and have read plenty on the data model, but we
>> wanted to poll for thoughts on how to best handle this structure.
>>
>> We have simple objects that have and ID and we want to maintain a histor=
y
>> of all the revisions.
>>
>> e.g.
>> MyObject:
>> =A0=A0=A0 ID (long)
>> =A0=A0=A0 name
>> =A0=A0=A0 other fields
>> =A0=A0=A0 update time (long [date])
>>
>>
>> Any time the object changes, we'll store down a new version of the objec=
t
>> (same ID, but different update time and other fields).=A0 We need to be =
able
>> to query out what the object was as-of any time historically.=A0 We also=
 need
>> to be able to query out what some or all of the items of this object typ=
e
>> were as-of any time historically..
>>
>> In SQL, we'd just find the max(id) where update time < queried_as_of_tim=
e
>>
>> In Cassandra, we were thinking of modeling as follows:
>>
>> CF:=A0 MyObjectType
>> Super-Column: ID of object (e.g. 625)
>> Column:=A0 updatetime=A0 (e.g. "1000245242")
>> Value: byte[] of serialized object
>>
>> We were thinking of using the OrderingPartitioner and using range querie=
s
>> against the data.
>>
>> Does this make sense?=A0 Are we approaching this in the wrong way?
>>
>> Thanks a lot
>>
>>
>>
>
>


--=20
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com