Deeper inside there is a diagram:
https://raw.githubusercontent.com/cockroachdb/cockroach/master/docs/media/sql-nosql-newsql.png
They compare to NoSQL along with Riak, HBase and Cassandra.
Of course you CAN have a Cassandra cluster which is not fully available with
loss of a dc nor
+1 for executeAsync – had a long time to argue that it’s not bad as with good
old rdbms.
Gesendet von meinem Windows 10 Phone
Von: Arvydas Jonusonis
Gesendet: Samstag, 18. März 2017 19:08
An: user@cassandra.apache.org
Betreff: Re: How can I scale my read rate?
..then you're not taking
Hi,
youre right – one seek with hit in the partition key cache and two if not.
Thats the theory – but two thinge to mention:
First, you need two seeks per sstable not per entire read. So if you data is
spread over multiple sstables on disk you obviously need more then two reads.
Think of
Hi,
doing a quick scan over the thread two things that came into my mind:
Frist, did the restore copy the sstables to the right machines back? Node As
data to node A and so on?
Second, did you run full repairs on every node? Not just incremental ones which
now is the default?
Also a look
Hi,
your primary goal is to fetch a user by dept_id and user_id and additionally
keep versions of the user data?
{
dept_id text,
user_id text,
mod_date timestamp,
user_name text,
PRIMARY KEY ((dept_id,user_id), mod_date)
WITH CLUSTERING ORDER BY (mod_date DESC);
}
There is a
Hi Jerry,
the compaction strategy just tells Cassandra how to compact your sstables and
with TWCS when to stop compacting further. But of course your data can and most
likely will live in multiple sstables.
The magic that happens is the the coordinator node for your request will merge
the
