Franc, We manage our schema through the Astyanax driver. It runs in a listener at application startup. We read a self-defined schema version, update the schema if needed based on the version number, and then write the new schema version number. There is a chance two or more app servers will try to update the schema at the same time but in our testing we haven't seen any problems result from this even when we forced many servers to all update the schema with many different updates at the same time. And besides we typically do a rolling restart anyway.
Todd, Mutagen Cassandra looks pretty similar to what we're doing, but is perhaps a bit more elegant. Will take a look at that now :) Cheers On Mon, Jul 1, 2013 at 5:55 PM, Franc Carter <franc.car...@sirca.org.au>wrote: > On Tue, Jul 2, 2013 at 10:33 AM, Todd Fast <t...@digitalexistence.com>wrote: > >> Franc-- >> >> I think you will find Mutagen Cassandra very interesting; it is similar >> to schema management tools like Flyway for SQL databases: >> > > Oops - forgot to mention in my original email that we will be looking into > Mutagen Cassandra in the medium term. I'm after something with a low > barrier to entry initially as we are quite time constrained. > > cheers > > >> >> Mutagen Cassandra is a framework (based on Mutagen) that provides schema >>> versioning and mutation for Apache Cassandra. >>> >>> Mutagen is a lightweight framework for applying versioned changes (known >>> as mutations) to a resource, in this case a Cassandra schema. Mutagen takes >>> into account the resource's existing state and only applies changes that >>> haven't yet been applied. >>> >>> Schema mutation with Mutagen helps you make manageable changes to the >>> schema of live Cassandra instances as you update your software, and is >>> especially useful when used across development, test, staging, and >>> production environments to automatically keep schemas in sync. >> >> >> >> https://github.com/toddfast/mutagen-cassandra >> >> Todd >> >> >> On Mon, Jul 1, 2013 at 5:23 PM, sankalp kohli <kohlisank...@gmail.com>wrote: >> >>> You can generate schema through the code. That is also one option. >>> >>> >>> On Mon, Jul 1, 2013 at 4:10 PM, Franc Carter >>> <franc.car...@sirca.org.au>wrote: >>> >>>> >>>> Hi, >>>> >>>> I've been giving some thought to the way we deploy schemas and am >>>> looking for something better than out current approach, which is to use >>>> cassandra-cli scripts. >>>> >>>> What do people use for this ? >>>> >>>> cheers >>>> >>>> -- >>>> >>>> *Franc Carter* | Systems architect | Sirca Ltd >>>> <marc.zianideferra...@sirca.org.au> >>>> >>>> franc.car...@sirca.org.au | www.sirca.org.au >>>> >>>> Tel: +61 2 8355 2514 >>>> >>>> Level 4, 55 Harrington St, The Rocks NSW 2000 >>>> >>>> PO Box H58, Australia Square, Sydney NSW 1215 >>>> >>>> >>>> >>> >> > > > -- > > *Franc Carter* | Systems architect | Sirca Ltd > <marc.zianideferra...@sirca.org.au> > > franc.car...@sirca.org.au | www.sirca.org.au > > Tel: +61 2 8355 2514 > > Level 4, 55 Harrington St, The Rocks NSW 2000 > > PO Box H58, Australia Square, Sydney NSW 1215 > > >
