Re: Using Cli to create a column family with column name metadata question

2011-11-04 Thread Jonathan Ellis 
[Moving to user@]

Because Cassandra's sparse data model supports using rows as
"materialized views," having non-UTF8 column names is common and
totally valid.

On Fri, Nov 4, 2011 at 5:19 AM, Arsene Lee
 wrote:
> Hi,
>
> I'm trying to use Column Family's metadata to do some validation. I found out 
> that in Cassandra's CLI CliClient.java code when trying to create a column 
> family with column name metadata. It is based on CF's comparator type to 
> convert the name String to ByteBuffer. I'm wondering if there is any 
> particular reason for this? For the column name metadata shouldn't it be 
> easier just to all use UTF8Type. Because if CF's comparator is other than 
> UTF8Type, it is hard to convert the column name back.
>
> Regards,
>
> Arsene Lee
>



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

Using Cli to create a column family with column name metadata question

2011-11-04 Thread Arsene Lee 
Hi,

I'm trying to use Column Family's metadata to do some validation. I found out 
that in Cassandra's CLI CliClient.java code when trying to create a column 
family with column name metadata. It is based on CF's comparator type to 
convert the name String to ByteBuffer. I'm wondering if there is any particular 
reason for this? For the column name metadata shouldn't it be easier just to 
all use UTF8Type. Because if CF's comparator is other than UTF8Type, it is hard 
to convert the column name back.

Regards,

Arsene Lee