On Wed, Jan 6, 2016 at 12:54 PM, Chris Burroughs <chris.burrou...@gmail.com> wrote:
> I work with Amir and further experimentation I can shed a little more > light on what exactly is going on under the hood. For background our goal > is to take data that is currently being read and written to via thrift, > switch reads to CQL, and then switch writes to CQL. This is in alternative > to deleting all of our data and starting over, or being forever struck on > super old thrift clients (both of those options obviously suck.) The data > models involved are absurdly simple (and single key with a handful of > static columns). ... > The problem with that approach is that manually editing the local schema > tables in live cluster is wildly dangerous. I *think* this would work: * Make triple sure no schema changes are happening on the cluster. * Update schema tables on each node --> drain --> restart I think that would work too, and probably be lower risk than modifying on one and trying to get the others to pull via resetlocalschema. But I agree it seems "wildly dangerous". FWIW, I think your case may be the case the project hopes to handle in https://issues.apache.org/jira/browse/CASSANDRA-10857 ? =Rob
