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 t
I agree having two tools is no good. I ended up discussing this in the IRC
channel for a bit yesterday for this column family.
1. create column family BrowserStuff
2. with column_type = 'Standard'
3. and comparator = 'UTF8Type'
4. and default_validation_class = 'UTF8Type'
5.
> Cassandra 2.0.4 cli is informing me that it will no longer exist in the
next major.
I know you meant 3.0 by "next major" but just for the sake of not confusing
anyone reading, the current plan is to remove the cassandra-cli in Cassandra
3.0 which will not be the next major release (the next majo
I am also curious as to how users will manage Thrift-based tables without
the cli.
PyCassaShell comes to mind, as does using Thrift-based clients.
On Tue, Feb 4, 2014 at 9:53 AM, Edward Capriolo wrote:
> Cassandra 2.0.4 cli is informing me that it will no longer exist in the
> next major.
>
> H
Cassandra 2.0.4 cli is informing me that it will no longer exist in the
next major.
How will users adjust the meta data of non cql column families and other
cfs that do not fit into the cql model?
--
Sorry this was sent from mobile. Will do less grammar and spell check than
usual.
