7;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
; 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 creat
mailto:dri...@gmail.com]
Sent: Tuesday, November 08, 2011 9:49 AM
To: user@cassandra.apache.org
Subject: Re: Using Cli to create a column family with column name metadata
question
On Mon, Nov 7, 2011 at 7:36 PM, Arsene Lee
wrote:
> Hi,
>
> Thanks for the replay. I'm not talking about the
Hi,
We are trying to use snapshot for backup and restore. We found out that
snapshot doesn't take secondary indexes.
We are wondering why is that? And is there any way we can rebuild the secondary
index?
Regards,
Arsene
here is a reason for excluding them. Is this causing a problem
right now ?
Aaron
On 3 May 2011, at 20:22, Arsene Lee
wrote:<https://issues.apache.org/jira/browse/CASSANDRA-2470>
Hi,
We are trying to use snapshot for backup and restore. We found out that
snapshot doesn’t take secondary indexe
