Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
MIME-Version: 1.0
References: <CD1F2E80-645D-49EA-A9E3-069FDC4D5DAF@gracenote.com>
In-Reply-To: <CD1F2E80-645D-49EA-A9E3-069FDC4D5DAF@gracenote.com>
From: Jonathan Haddad <jon@jonhaddad.com>
Date: Wed, 10 Feb 2016 20:22:01 +0000
Message-ID: 
 <CACUnPaBBtM-R6jd4kpUJo-3AxEAQoaVJ6FN03jnbEWbDEYhyyw@mail.gmail.com>
Subject: Re: Schema Versioning
To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Content-Type: multipart/alternative; boundary=089e0149544666f62d052b7030c4

--089e0149544666f62d052b7030c4
Content-Type: text/plain; charset=UTF-8

I wrote most of the cqlengine keyspace & table management pieces of the
Python driver to solve this exact problem.  Instead of working with a
series of statements for creating tables & managing columns, we simply
created classes in Python and sync'ed them to the DB.  It automatically
figured out what was needed and took care of it.

DB Models:
https://datastax.github.io/python-driver/api/cassandra/cqlengine/models.html
Syncing to DB:
https://datastax.github.io/python-driver/api/cassandra/cqlengine/management.html#cassandra.cqlengine.management.sync_table

If you're not using Python, I'm not sure what options you have, I'm not
much help there.

On Wed, Feb 10, 2016 at 12:05 PM Joe Bako <jbako@gracenote.com> wrote:

> Hi all,
>
> I am curious what techniques are used by others to manage schema changes
> over time in Cassandra.
>
> 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).
>
> The former allows you to easily see schema changes over time in your SCM
> history, the latter keeps a history of actual DDL applied against the
> database objects.  What options are available for C* and what are people
> using?
>
> Joe Bako
> Software Architect
> Gracenote, Inc.
> http://www.gracenote.com/
>
>

--089e0149544666f62d052b7030c4
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I wrote most of the cqlengine keyspace &amp; table managem=
ent pieces of the Python driver to solve this exact problem.=C2=A0 Instead =
of working with a series of statements for creating tables &amp; managing c=
olumns, we simply created classes in Python and sync&#39;ed them to the DB.=
=C2=A0 It automatically figured out what was needed and took care of it. =
=C2=A0<div><br></div><div>DB Models:=C2=A0<a href=3D"https://datastax.githu=
b.io/python-driver/api/cassandra/cqlengine/models.html">https://datastax.gi=
thub.io/python-driver/api/cassandra/cqlengine/models.html</a></div><div>Syn=
cing to DB: <a href=3D"https://datastax.github.io/python-driver/api/cassand=
ra/cqlengine/management.html#cassandra.cqlengine.management.sync_table">htt=
ps://datastax.github.io/python-driver/api/cassandra/cqlengine/management.ht=
ml#cassandra.cqlengine.management.sync_table</a><br></div><div><br></div><d=
iv>If you&#39;re not using Python, I&#39;m not sure what options you have, =
I&#39;m not much help there.</div></div><br><div class=3D"gmail_quote"><div=
 dir=3D"ltr">On Wed, Feb 10, 2016 at 12:05 PM Joe Bako &lt;<a href=3D"mailt=
o:jbako@gracenote.com">jbako@gracenote.com</a>&gt; wrote:<br></div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex">Hi all,<br>
<br>
I am curious what techniques are used by others to manage schema changes ov=
er time in Cassandra.<br>
<br>
Modern RDBMS tools can compare schemas between DDL object definitions and l=
ive databases and generate change scripts accordingly.=C2=A0 Older techniqu=
es 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 be=
en run previously or not (indicated in the script table).<br>
<br>
The former allows you to easily see schema changes over time in your SCM hi=
story, the latter keeps a history of actual DDL applied against the databas=
e objects.=C2=A0 What options are available for C* and what are people usin=
g?<br>
<br>
Joe Bako<br>
Software Architect<br>
Gracenote, Inc.<br>
<a href=3D"http://www.gracenote.com/" rel=3D"noreferrer" target=3D"_blank">=
http://www.gracenote.com/</a><br>
<br>
</blockquote></div>

--089e0149544666f62d052b7030c4--