foo. Will this work?
>
> From: aaron morton [mailto:aa...@thelastpickle.com]
> Sent: Sunday, November 11, 2012 3:39 PM
> To: user@cassandra.apache.org
> Subject: Re: CREATE COLUMNFAMILY
>
> Also most idomatic clients use the information so they can return the
> appro
at by adding
metadata for foo. Will this work?
From: aaron morton [mailto:aa...@thelastpickle.com]
Sent: Sunday, November 11, 2012 3:39 PM
To: user@cassandra.apache.org
Subject: Re: CREATE COLUMNFAMILY
Also most idomatic clients use the information so they can return the
appropriate type t
ember 11, 2012 9:37 AM
> To: user@cassandra.apache.org
> Subject: Re: CREATE COLUMNFAMILY
>
> If you supply metadata cassandra can use it for several things.
>
> 1) It validates data on insertion
> 2) Helps display the information in human readable formats in tools like the
> C
...@gmail.com]
Sent: Sunday, November 11, 2012 9:37 AM
To: user@cassandra.apache.org
Subject: Re: CREATE COLUMNFAMILY
If you supply metadata cassandra can use it for several things.
1) It validates data on insertion
2) Helps display the information in human readable formats in tools like the
CLI and
If you supply metadata cassandra can use it for several things.
1) It validates data on insertion
2) Helps display the information in human readable formats in tools
like the CLI and
sstabletojson
3) If you add a built-in secondary index the type information is
needed, strings sort differently the
You've set a comparator for the super column names, but not the sub columns.
e.g.
[default@dev] set data['31']['address']['city']='noida';
org.apache.cassandra.db.marshal.MarshalException: cannot parse 'city' as hex
bytes
[default@dev] set data['31']['address'][utf8('city')]='noida';
Value
