> Compact storage is the schemaless of old.
Right. That comes with the downside of picking one :) It does not seem
the compact storage is the default choice for the the future. As well as
interop with the thrift/cli world, I also find it hard to reason about
row caching with CQL defined table
@Bill
Are you saying that now cassandra is less schema less ? :)
Compact storage is the schemaless of old.
On Tuesday, November 27, 2012, Bill de hÓra wrote:
>> I'm not sure I always
>> understand what people mean by "schema less"
>> exactly and I'm curious.
>
> For 'schema less', given this -
> I'm not sure I always
> understand what people mean by "schema less"
> exactly and I'm curious.
For 'schema less', given this -
{{{
cqlsh> use example;
cqlsh:example> CREATE TABLE users (
... user_name varchar,
... password varchar,
... gender varchar,
... session_token varchar,
... state
Da: sylv...@datastax.com
> The error message is indeed somewhat misleading and I've just committed a fix
> to return a better message. But at the end of the day, the > limitation is
> that ORDER BY is just not supported with 2ndary indexes.
mmm this is not good news for the model I just designe
>
> Thanks for the answer ... the error described before is: "ORDER BY is only
> supported when the partition key is restricted by an EQ or an IN."
> But I don't see how I didn't respect the rule ...
>
The error message is indeed somewhat misleading and I've just committed a
fix to return a better
>> Aaron first of all thanks for your precious help everytime ….
>Thanks for using Cassandra since version 0.6 :)
ahahah :-)
>There are two types of CQL 3 tables, regular ones and those that use "COMPACT
STORAGE". Regular CQL 3 tables are not visible to Thrift as they store some
extra data tha
On Mon, Nov 26, 2012 at 8:41 AM, aaron morton wrote:
> > Is there any noticeable performance difference between thrift or CQL3?
> Off the top of my head it's within 5% (maybe 10%) under stress tests. See
Eric's talk at the Cassandra SF conference for the exact numbers.
Eric's benchmark results was
> Aaron first of all thanks for your precious help everytime ….
Thanks for using Cassandra since version 0.6 :)
> What it means that it will support "concurrent schema modifications?"
Previously we said you can change the schema online, but only do it at one node
at a time. In v1.2 you can have m
Aaron first of all thanks for your precious help everytime
Some resources for CQL 3, it may match your needs. If not you can still use
Thrift through your favourite client...There have been a few articles on the DS
blog http://www.datastax.com/dev/blogA talk at the conference by Eric
htt
> Now I am going to write a new application using cassandra so I started
> reading
> documentation in order to "model" the new db using all the new features and
> not
> reinventing the wheel.
Some resources for CQL 3, it may match your needs. If not you can still use
Thrift through your favour
Hi all,
I'm in production with cassandra since version 0.6 then upgraded to 0.7 and
finally to 1.0.
If I look at my schema now it's "senseless" to be on 1.0 but many things
changed from 0.6 ... secondary indexes, counters, expiring columns and more.
Now I am going to write a new application using
11 matches
Mail list logo
