Using the methods on the Bytes class would be preferable. The byte[]
related methods on UuidHelper should have been deprecated with the Bytes
class was introduced...
e.g. new Bytes(col.getName()).toUuid()
Cheers,
Dan
On Thu, Dec 2, 2010 at 10:26 AM, Frank LoVecchio wrote:
> Actually, it was a
Actually, it was a class issue at this line:
System.*out*.println("NAME: " + UUID.*nameUUIDFromBytes*(col.getName()));
The native Pelops class timeUuidHelper is what should be used.
On Wed, Dec 1, 2010 at 4:16 PM, Aaron Morton wrote:
> When you say "I want to get rows starting from a Super Colu
When you say "I want to get rows starting from a Super Column..." it's a bit confusing. Do you want to get super columns from a single row, or multiple rows? I'm assuming you are talking about getting columns from a single row / key as that's what your code does.For the pelops code, it looks OK but
Hey Aaron,
Yes, in regards to SCF definition, you are correct:
name: Sensor
column_type: Super
compare_with: TimeUUIDType
gc_grace_seconds: 864000
keys_cached: 1.0
read_repair_chance: 1.0
rows_cached: 0.0
I'm not quite sure I follow you, though, as
The Partitioner applies to the row keys, not the columns. Their order is determined by the compare_with and compare_subcolumns_with CF settings So where you say "get the last 25 inserts for a key" I'm translating that into "get the most recent 25 super columns for a row, where the super column name
Is it possible to perform paginated queries using Random Partitioner in 0.7
with Super Column Families whose Super Columns are UUID's? I don't believe
it is, based on this article:
http://ria101.wordpress.com/2010/02/22/cassandra-randompartitioner-vs-orderpreservingpartitioner,
and my attempts wit
