,
- Original Message -
From: user@cassandra.apache.org
To:user@cassandra.apache.org
Cc:
Sent:Wed, 9 Jan 2013 23:14:25 +0100
Subject:Re: Wide rows in CQL 3
I'd be clear, CQL3 is meant as an upgrade from thrift. Not a mandatory
one, you
can stick to thrift if you don't think CQL3 is better. But if you
:
Sent:
Wed, 9 Jan 2013 23:14:25 +0100
Subject:
Re: Wide rows in CQL 3
I'd be clear, CQL3 is meant as an upgrade from thrift. Not a mandatory one,
you
can stick to thrift if you don't think CQL3 is better. But if you do decide to
upgrade, you should see CQL3 non compact tables as the new
...@gmail.com
Reply-To: user@cassandra.apache.orgmailto:user@cassandra.apache.org
user@cassandra.apache.orgmailto:user@cassandra.apache.org
Date: Wednesday, January 9, 2013 9:51 AM
To: user user@cassandra.apache.orgmailto:user@cassandra.apache.org
Subject: Wide rows in CQL 3
We use the thrift bindings
I'm currently in the process of porting my app from Thrift to CQL3 and it
seems to me that the underlying storage layout hasn't really changed
fundamentally. The difference appears to be that CQL3 offers a neater
abstraction on top of the wide row format. For example, in CQL3, your query
results
I ask myself this every day. CQL3 is new way to do things, including wide
rows with collections. There is no upgrade path. You adopt CQL3's sparse
tables as soon as you start creating column families from CQL. There is not
much backwards compatibility. CQL3 can query compact tables, but you may
There is no upgrade path.
I don't think that's true. The goal of the blog post you've linked is to
discuss that upgrade path (and in particular show that for the most part,
you
can access your thrift data from CQL3 without any modification whatsoever).
You adopt CQL3's sparse tables as soon as
By no upgrade path I mean to say if I have a table with compact storage I
can not upgrade it to sparse storage. If i have an existing COMPACT table
and I want to add a Map to it, I can not. This is what I mean by no upgrade
path.
Column families that mix static and dynamic columns are pretty
Also I have to say I do not get that blank sparse column.
Ghost ranges are a little weird but they don't bother me.
1 its a row of nothing. The definition of a waste.
2 suppose of have 1 billion rows and my distribution is mostly rows of 1 or
2 columns. My database is now significantly bigger.
On 10 Jan 2013, at 01:30, Edward Capriolo edlinuxg...@gmail.com wrote:
Column families that mix static and dynamic columns are pretty common. In
fact it is pretty much the default case, you have a default validator then
some columns have specific validators. In the old days people used to
