Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of gdusbabek@gmail.com designates
 74.125.82.44 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:reply-to:in-reply-to:references:date:message-id
         :subject:from:to:content-type:content-transfer-encoding;
        b=F8WM4iuGnE6fUrnWPrz7lxqvxMZcbZnldahG6YE/3iMj2grWbvdnjnF3mdBhw6j1iy
         RNyw0KprGKeY12PagpHvcSbGsFrMwbufMaGfQwkyMbUueNHgoADaYqL/th37f1xx6lPE
         K3jUWD4ggt6mf1o1hKhgFe9M9BFG3wuqG1QLw=
MIME-Version: 1.0
Reply-To: gdusbabek@gmail.com
In-Reply-To: <4C6DB797.9010301@qualcomm.com>
References: <4C6DB797.9010301@qualcomm.com>
Date: Fri, 20 Aug 2010 08:05:13 -0500
Message-ID: <AANLkTim45LTcwjrvm3wY=eQar3_gZvJnZvAptPgC-4Jz@mail.gmail.com>
Subject: Re: Replication factor and other schema changes in >= 0.7
From: Gary Dusbabek <gdusbabek@gmail.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

It is coming.  In fact, I started working on this ticket yesterday.
Most of the settings that you could change before will be modifiable.
Unfortunately, you must still manually perform the repair operations,
etc., afterward.

https://issues.apache.org/jira/browse/CASSANDRA-1285

Gary.


On Thu, Aug 19, 2010 at 18:00, Andres March <amarch@qualcomm.com> wrote:
> How should we go about changing the replication factor and other keyspace
> settings now that it and other KSMetaData are no longer managed in
> cassandra.yaml?
>
> I found makeDefinitionMutation() in the Migration class and see that it i=
s
> called for the other schema migrations.=A0 There just seems to be a big g=
ap in
> the management API for the KSMetaData we might want to change.
> --
> Andres March
> amarch@qualcomm.com
> Qualcomm Internet Services