Is it possible to mix both Standard and Super columns in the same
Column Family? One of our Perl developers seems to have this working,
but I have been using the Java Pelops client and have been unable to
make this happen.

I'm not asking how to do with Pelops as I'll bug those guys if it is
possible, but can standard and super columns be mixed in the same
column family?

Here's the script he was using (which looks like he is able to define
a column_type of super for some the columns but not others):

create column family users
    with comparator = UTF8T
    and key_validation_class=UTF8TYpe
    and compression_options = { sstable_compression:SnappyCompressor,
chunk_length_kb:64}
    and column_metadata = [
    { column_name: FirstName, validation_class : UTF8Type},
    { column_name: LastName, validation_class : UTF8Type},
    { column_name: FavStore, validation_class : IntegerType},
    { column_type: super, column_name: HomeAddress
    , column_metadata = [
      { column_name: Street, validation_class : UTF8Type},
      { column_name: State, validation_class : UTF8Type},
      { column_name: Zip, validation_class : LongType} ] },
    { column_type: super, column_name: WorkAddress
    , column_metadata = [
    { column_name: Street, validation_class : UTF8Type},
    { column_name: State, validation_class : UTF8Type},
    { column_name: Zip, validation_class : LongType} ] },
    { column_type: super, column_name: Favorites }
    ];

And here's the CLI output which for the column_types of super
indicates a hash value instead of a scaler.

list users;
Using default limit of 100
-------------------
RowKey: bobjones
=> (column=FavStore, value=59580595188280, timestamp=1330696438)
=> (column=Favorites, value=HASH(0x3618bc0), timestamp=1330696438)
=> (column=FirstName, value=Bob, timestamp=1330696438)
=> (column=HomeAddress, value=HASH(0x3618b30), timestamp=1330696438)
=> (column=LastName, value=Jones, timestamp=1330696438)
=> (column=WorkAddress, value=HASH(0x3619688), timestamp=1330696438)


Thanks in advance.

cb

-- 
Christopher Bowland
cbowl...@gmail.com

Reply via email to