cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Ellis <>
Subject Re: CQL3 question
Date Mon, 13 May 2013 17:02:33 GMT
using GET or LIST from the cli will do what you want

it's a bad idea to have One Big Partition, since partitions by nature
are not spread across multiple machines.  in general you'll want to
keep partitions under ~ 1M cells or ~100K CQL3 rows.

On Sun, May 12, 2013 at 12:53 AM, Sam Mandes <> wrote:
> Hello Jonathan,
> I read your blog
> post: and enjoyed
> it so much. I am new to the NoSQL world, I came from the SQL world.
> I noticed that Cassandra is pushing CQL3 more, it's even recommended to use
> CQL3 for new projects instead of the Thrift API. I believe Cassandra is
> going to drop Thrift one day. I know that one can use the compact storage to
> allow backward compatibility. And I know that CQL3 uses the new binary
> protocol instead of Thrift now. I believe they both use the same storage
> engine. (I still do not understand why they are incompatible!)
> Thus, I was wondering is there is a possible way that I can view the tables
> created with CQL3 in a lower-level view like I used with Thrift? I mean I
> can view the tables as simply CFs, as how rows are exactly stored, just
> something to expose the internal representation?
> I've another question, when using compact storage and creating a table with
> composite primary key, Cassandra uses a single rows with multiple columns
> but if I've lots of items and the columns limit is 20 billion, how can this
> be avoided. I do not understand how CQL3 unpacking helps in this situation?
> Sorry for any inconvenience :)
> Thanks a lot,
> Sam

Jonathan Ellis
Project Chair, Apache Cassandra

View raw message