I sidestep this problem by using a Python script (pycassa-based) where I
configure my CFs. This way, it's reproducible and documented.
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/create-additional-secondary-index-tp6033574p6033683.html
Yes, that is a known weakness of the current cli interface to column_metadata.
On Wed, Feb 16, 2011 at 3:16 PM, Yueyu Fu wrote:
> Hi,
>
> I'm trying to add a new secondary index on a CF which already have a
> secondary index by calling "update column family".
>
> But the CF was left with just th
Hi,
I'm trying to add a new secondary index on a CF which already have a secondary
index by calling "update column family".
But the CF was left with just the new secondary index and the old index
disappeared. AFAIK, the only way to keep both indices was to include the old
secondary index in th