On Thu, Sep 2, 2010 at 6:25 PM, Mike Peters
wrote:
>
> My concerns are -
> #1. Will every single node end up with 4k folders under /cassandra/data/?
>
Yes (and you should review how Cassandra works if that is a question for you).
> #2. Performance: Will Cassandra work better with a single keyspa
I read an article about using CAGES with Cassandra to achieve locking
and transaction...
Here is the link :
http://ria101.wordpress.com/2010/05/12/locking-and-transactions-over-cassandra-using-cages/
On 9/5/10, Michal Augustýn wrote:
> Hello,
>
> we can read everywhere that Cassandra (and simil
Hi Michal,
Did you read the PDF Stu sent over, start to finish? There are several
different approaches described there.
With Cassandra, what we found works best for pagination:
* Keep a separate 'total_records' count and increment/decrement it on
every insert/delete
* When getting slices, pa
I know that "Prev/Next" is good solution for web applications. But when I
want to access data from another application or when I want to access pages
randomly...
I don't know the internal structure of memtables etc., so I don't know if
columns in row are indexable. If now, then I just want to tran
Cassandra supports the recommended approach from:
http://www.percona.com/ppc2009/PPC2009_mysql_pagination.pdf
For large numbers of items, skip + limit is extremely inefficent.
-Original Message-
From: "Michal Augustýn"
Sent: Sunday, September 5, 2010 5:39am
To: user@cassandra.apache.org
Read repair chance looks to be an awesome feature. We have a pretty
high cache hit rate so I would assume read repair chance would reduce
a lot of bandwidth and disk activity across our cluster. Does anyone
have some statistics or experiences they want to share?
Edward
Hello,
we can read everywhere that Cassandra (and similar NoSQL solutions) doesn't
support full ACID and (when we want to have ACID) we have to implement ACID
in higher layers of our application. Are there some good resources on how to
implement ACID on higher layers? I.e. how to implement reposit
Hello,
probably this is feature request. Simply, I would like to have support for
standard pagination (skip + limit) in GetSlice Thrift method. Is this
feature on the road map?
Now, I have to perform GetSlice call, that starts on "" and "limit" is set
to "skip" value. Then I read the last column
