cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carlos Alonso <i...@mrcalonso.com>
Subject Re: Schema Versioning
Date Thu, 11 Feb 2016 09:57:44 GMT
Here we use the Cassanity gem: https://github.com/jnunemaker/cassanity
This one suggests using schema migration files that are then registered in
a column family to keep track of the version.

Carlos Alonso | Software Engineer | @calonso <https://twitter.com/calonso>

On 10 February 2016 at 21:29, Alex Popescu <alexp@datastax.com> wrote:

>
> On Wed, Feb 10, 2016 at 12:05 PM, Joe Bako <jbako@gracenote.com> wrote:
>
>> Modern RDBMS tools can compare schemas between DDL object definitions and
>> live databases and generate change scripts accordingly.  Older techniques
>> included maintaining a version and script table in the database, storing
>> schema change scripts in a sequential fashion on disk, and iterating over
>> them to apply them against the target database based on whether they had
>> been run previously or not (indicated in the script table).
>
>
> Using DevCenter will give you some of these features (and future versions
> will add more). Just to give you a quick example, if using DevCenter to
> make schema changes it will offer the options of saving the final
> definition or just the set of changes applied (to an existing CQL file or a
> new one).
>
>
> --
> Bests,
>
> Alex Popescu | @al3xandru
> Sen. Product Manager @ DataStax
>
>

Mime
View raw message