Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of marko.asplund@gmail.com
 designates 209.85.219.49 as permitted sender)
MIME-Version: 1.0
From: Marko Asplund <marko.asplund@gmail.com>
Date: Fri, 26 Apr 2013 08:57:58 +0300
Message-ID: 
 <CANoUZR8MKLTygHnE2VCG8o185zePj8wpbq6Ug9fojkSv2TgzVw@mail.gmail.com>
Subject: Re: DB Change management tools for Cassandra?
To: user@cassandra.apache.org
Content-Type: text/plain; charset=UTF-8

John Sanda wrote:
> I had cobbled together a solution using Liquibase and the Cassandra JDBC
> driver. I started implemented it before the CQL driver was announced. The
> solution involved a patch and some Liquibase extensions which live at
> https://github.com/jsanda/cassandra-liquibase-ext. The patch will go into
> the 3.0 release of Liquibase. I developed the extensions against the 2.x
> code base. Changes were introduced for Liquibase 3.0 that broken the
> extensions I developed. At that point I decided to pursue a simpler
> solution (though I think Liquibase is a great tool for relational
> databases). Please update the list with any efforts as I am definitely
> interested!

thanks John!

So, did I understand correctly that you've discontinued developing
your extension, but that your patch will go into Liquibase 3.0, right?
Will the patch add some support for Cassandra database change
management in Liquibase that's usable by developers or is it just for
being able to create Cassandra extensions for Liquibase?

What kind of approach did you take with the simpler solution?

I also came across the following Liquibase Cassandra extension:
https://github.com/liquibase/liquibase-cassandra

Anyone have experience with this one?


marko