Thank you guys ...
On 2/16/2011 1:36 PM, Matthew Dennis wrote:
+1 on avoiding OPP
On Wed, Feb 16, 2011 at 3:27 PM, Tyler Hobbs<ty...@datastax.com> wrote:
Thanks for you input, but we have a set key that consists of name:timestamp
that we are using.. and we need to also retrieve the oldest data as well..
Then you'll need to denormalize and store every row three ways: timestamp,
inverted timestamp, and normal, if you want to be able to access them in all
three ways using OPP.
I would recommend not using OPP and just using timeline rows. Here's a
fantastic discussion of OrderPreservingPartitioner vs
RandomPartitioner<http://ria101.wordpress.com/2010/02/22/cassandra-randompartitioner-vs-orderpreservingpartitioner/>
.
--
Tyler Hobbs
Software Engineer, DataStax<http://datastax.com/>
Maintainer of the pycassa<http://github.com/pycassa/pycassa> Cassandra
Python client library
--
Alaa Zubaidi
PDF Solutions, Inc.
333 West San Carlos Street, Suite 700
San Jose, CA 95110 USA
Tel: 408-283-5639 (or 408-280-7900 x5639)
fax: 408-938-6479
email: alaa.zuba...@pdf.com