On Wed, May 23, 2012 at 3:07 PM, aaron morton wrote:
> When you say
>
> comparator=BytesType
>
>
> You are telling cassandra that the column names in the CF's are just
> bytes. But when you create the column meta data you are specifying the
> column names as strings.
>
> use UTF8Type as the compa
When you say
> comparator=BytesType
You are telling cassandra that the column names in the CF's are just bytes. But
when you create the column meta data you are specifying the column names as
strings.
use UTF8Type as the comparator.
Cheers
-
Aaron Morton
Freelance Develope
I an not able to reproduce this in cli.
On 22-May-2012 8:12 PM, "Roshan Dawrani" wrote:
> Can you please let me know why? Because I have created very similar column
> familes many times with comparator = BytesType, and never run into this
> issue before.
>
> Here is an example:
>
> --
Can you please let me know why? Because I have created very similar column
familes many times with comparator = BytesType, and never run into this
issue before.
Here is an example:
ColumnFamily: Client
Key Validation Class: or
Change your comparator to utf8type.
On 22-May-2012 4:32 PM, "Roshan Dawrani" wrote:
> Hi,
>
> I use Cassandra 0.8.5 and am suddenly noticing some strange behavior. I
> run a "create column family" command with some column meta-data and it runs
> fine, but when I do "describe keyspace", it shows m
Hi,
I use Cassandra 0.8.5 and am suddenly noticing some strange behavior. I run
a "create column family" command with some column meta-data and it runs
fine, but when I do "describe keyspace", it shows me different column names
for those index columns.
a) Here is what I run:
"create column family
Hi,
I use Cassandra 0.8.5 and am suddenly noticing some strange behavior. I run
a "create column family" command with some column meta-data and it runs
fine, but when I do "describe keyspace", it shows me different column names
for those index columns.
a) Here is what I run:
"create column family
