Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of chris.burroughs@gmail.com
 designates 209.85.216.181 as permitted sender)
Message-ID: <52F3933C.7080308@gmail.com>
Date: Thu, 06 Feb 2014 08:50:52 -0500
From: Chris Burroughs <chris.burroughs@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:24.0) Gecko/20100101 Icedove/24.0
MIME-Version: 1.0
To: user@cassandra.apache.org
Subject: Re: what tool will create noncql columnfamilies in cassandra 3a
References: 
 <CAENxBwwmcg4KGwgt4FsrOjVVmYg9EXeAyBOQ-DsaZq+rwN2_Sg@mail.gmail.com>
	<CAFz1oU1E7mG9-jy+-9AqC2CG3B2geTL12dsn=3QqBGrECMUJ9g@mail.gmail.com>
 <CAKkz8Q35hBQkCLv45DapNvD-ysdphqByZ7MJ-ta8vYyZnOGsMg@mail.gmail.com>
In-Reply-To: 
 <CAKkz8Q35hBQkCLv45DapNvD-ysdphqByZ7MJ-ta8vYyZnOGsMg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 02/05/2014 04:57 AM, Sylvain Lebresne wrote:
>> >How will users adjust the meta data of non cql column families
> The rational for removing cassandra-cli is mainly that maintaining 2 fully
> featured command line interface is a waste of the project resources in the
> long
> run. It's just a tool using the thrift interface however and you'll still be
> able to adjust metadata through the thrift interface as before. As Patricia
> mentioned, there is even some existing interactive options like pycassaShell
> in the community.

It's also wasteful for the community to maintain multiple post 3.0 forks 
for cassandra-cli so they can continue using Cassandra.  It would be 
more efficient if they cool pool their resources in a central place, 
like a code repo at Apache.