That looks like an error thrown from CFMetaData, telling you it's not possible to change a Standard CF to a Super CF. Which seems logical to me, how would it move the data from a standard CF to a super CF?
You'll need to create a new Super CF and migrate the data manually.
On 29 Sep, 2010,at 10:15 AM, Frank LoVecchio <email@example.com> wrote:
I tried that method in Pelops, and this is the error I get when trying to to update a Column Family Type from Standard to Super:
InvalidRequestException(why:types do not match.)
I have last night's build of Cassandra.
On Tue, Sep 28, 2010 at 2:55 PM, Aaron Morton <firstname.lastname@example.org>
There is a system_update_column_family(CDef) function on the trunk, so it will be in 0.7-beta2. Take a look at the interface/cassandra.thrift .
I understand adding column family configuration fields using thrift in Pelops for system_add_column_family, and even renaming column families, but what about modifying the actual column family configuration values, e.g. read_repair_chance: 1.0 to read_repair_chance: .5 (as a poor example)?
On Tue, Sep 28, 2010 at 1:17 PM, Peter Schuller <email@example.com>
> Question regarding schema set-up and modification: I just set up the newestExpected in 0.7 where the configuration file is essentially just an example:
> nightly build of 0.7, imported our .yaml file after starting Cassandra, and
> everything is honky-dorey. We're not sure if Pelops is capable of modifying
> shema definitions, but it doesn't appear any changes we make to the .yaml
> file after the initial import go through (re-importing using schematool
> doesn't work).
Check out the system_* methods at the bottom of
> How could I change, for example, the rows_cached or name
> fields below on the fly without losing data? Is this possible?
interface/cassandra.thrift. I believe these are in working order for
/ Peter Schuller