Technically there could be data in an sstable with a later time stamp than
what exists in the memtable. Consider the use case of issuing a delete in
the future to avoid race conditions.
On Sat, Sep 5, 2015 at 10:42 AM Ray Sutton wrote:
> This documentation from Datastax may be helpful to understa
This documentation from Datastax may be helpful to understand the purpose
of memtables and sstables.
http://docs.datastax.com/en/cassandra/2.0/cassandra/dml/dml_write_path_c.html
Ray
On Sat, Sep 5, 2015 at 10:36 AM Anuj Wadehra wrote:
> Memtables are for storing writes in memory till they are f
Memtables are for storing writes in memory till they are flushed to disk as
sstables and once flushed, space gets released from commit logs too.. If your
are updating some columns only that data would be there in memtables not entire
row..Dont think of memtables as row cache..
This is my under
In this cases, assume we have 4-nodes cluster N1, N2, N3, and N4 and
replication factor is 3. Client c1 sends W1 = [k1,V1] to N1 (a
coordinator). A coordinator (N1) generates timestamp Mon 05-09-2015
11:30:40,200 (according to its local clock) and assigned it to W1 and sends
the W1 to the N2, N3,
Hi Team,
Please provide your I/P.
Is the data shored in Cassandra & Solr(documents) separately? If so how much
extra space is required in disk?
If I want to run adhoc queries on any column of a table in cassandra, should I
plan to index all the fields in solr or take some other approach?
Is cre
