Mailing-List: contact dev-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of
 gcdcd-cassandra-dev-1@m.gmane.org designates 80.91.229.12 as permitted
 sender)
To: dev@cassandra.apache.org
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: loading schema in trunk
Date: Tue, 13 Apr 2010 10:19:23 -0500
Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @
 Cienfuegos
Lines: 32
Message-ID: <87fx2z9y84.fsf@lifelogs.com>
References: <874ojgfwdu.fsf@lifelogs.com>
	<1271093989.8771.438.camel@erebus.lan> <87iq7wee76.fsf@lifelogs.com>
	<87wrwcb9l4.fsf@lifelogs.com> <1271111292.32464.19.camel@erebus.lan>
	<87sk70b77n.fsf@lifelogs.com>
	<u2o1c6fcff1004121825r4ddafdbeo4ede129e075e73f2@mail.gmail.com>
	<87d3y3bjs1.fsf@lifelogs.com>
	<m2h1c6fcff1004130557i6a948eaao869e985cf3262098@mail.gmail.com>
	<87vdbva2vm.fsf@lifelogs.com>
	<p2l1c6fcff1004130644w7d61d454ybbdad8374032ce96@mail.gmail.com>
	<1271167724.32464.55.camel@erebus.lan>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/24.0.50 (gnu/linux)
Cancel-Lock: sha1:0aRkJVt2t5HpwUcGjhsRptANsic=

On Tue, 13 Apr 2010 09:08:44 -0500 Eric Evans <eevans@rackspace.com> wrote: 

EE> On Tue, 2010-04-13 at 08:44 -0500, Gary Dusbabek wrote:
>> 2010/4/13 Ted Zlatanov <tzz@lifelogs.com>:
>> > Should the functionality be exposed only through JMX, through nodetool,
>> > or through cassandra-cli?  I'll create the ticket if you like and then I
>> > or whoever wants to can work on it.

>> I prefer thrift (and nodetool), but I'd like to hear thoughts from the
>> community.

EE> If we're going to do this, I suggest a separate utility scoped at
EE> migrating existing definitions from an 0.6 configuration (and nothing
EE> else), and then deprecate it right off the bat (read: for removal in
EE> 0.8).

EE> The point here is to be as clear as possible that it is transient, and
EE> shouldn't be adopted as a management tool.

I think everyone agrees loadSchemaFromXML can go away after 0.7 but just
to be clear, you don't think Cassandra after 0.7 should come bundled
with a tool that can dump, clear, and restore the schema?  It's trivial
to implement some very basic support for that without trying to provide
a full management tool.

I think it would be a big help for new users, troubleshooting (because
you don't depend on tollkit X or language Y to know the true schema from
the server's POV), those who want to share schema definitions and tests
without external dependencies, and sysadmins who don't want to install
another language to do a schema backup.

Ted