On Mon, May 31, 2010 at 8:52 PM, Jonathan Ellis wrote:
> OPP uses lexical ordering on the keys, which isn't going to be the
> same as the natural order for a time-based uuid.
*palmface*
On Sat, May 29, 2010 at 11:55 PM, Jonathan Ellis wrote:
> Cassandra supports slicing columns within a row in reversed order, but
> not iterating rows in reverse.
>
Thanks Jonathan
Hello!
I am using an OrderPreservingPartitioner and sequential UUID's as
keys. When I use get_range I frequently get an error indicating that
my start key is not before or equal to my finish key, which seems
impossible. The code to request slices looks like this:
sometime = Time.now
a = UUIDTools
I see the Ruby cassandra gem now supports :count for get_range, which
means I can get the first of my slice of records when using OPP, but I
can't get the last without get_range supporting a :reversed => true
option. Does the underlying API support reversing a slice?
Hi!
I am having trouble understanding the "column" terminology Cassandra
uses. I am developing in Ruby. I need to store data for vehicles which
will come in at different times and retrieve data for a specific
vehicle for specific slices of time. So each record could look like:
vehicle_id, { time