Yes, they are stored on disk like a normal table.
On Tue, Dec 13, 2016 at 2:31 PM, Kant Kodali wrote:
> Are Materialized views persisted on disk? sorry for the naive question.
>
Hi Joaquin,
Your best bet for a response will be on the spark-cassandra-connector
mailing list:
https://groups.google.com/a/lists.datastax.com/forum/#!forum/spark-connector-user
Hope you find your answer.
-Carl
On Wed, Jun 22, 2016 at 4:58 AM, Joaquin Alzola
wrote:
> Hi List
>
>
>
> I am tryi
The paxos state is written to a system table (system.paxos) on each of the
paxos coordinators, so it goes through the normal write path, including
persisting to the log and being stored in a memtable until being flushed to
disk. As such, the state can survive restarts. These states are not treated
This is set in the cassandra.yaml on each node independently; it doesn't
have to be same cluster-wide.
On Mon, Jan 4, 2016 at 3:59 PM, Ken Hancock wrote:
> I was surprised the other day to discover that this was a cluster-wide
> setting. Why does that make sense?
>
> In a heterogeneous cassand
Hi Soto,
You are going to have more luck using the C# driver list instead of the
cassandra-user list.
https://groups.google.com/a/lists.datastax.com/forum/#!forum/csharp-driver-user
-Carl
On Thu, Dec 17, 2015 at 3:01 PM, Sotirios Delimanolis
wrote:
> Hey,
>
> I wanted to ask here before I ope
In the case of an update to the source table where data is changed, a
tombstone will be generated for the old value and an insert will be
generated for the new value. This happens serially for the source
partition, so if there are multiple updates to the same partition, a
tombstone will be generate
These questions would be better addressed to the Spark Cassandra Connector
mailing list, which can be found here:
https://github.com/datastax/spark-cassandra-connector/#community
Thanks,
Carl
On Tue, Mar 3, 2015 at 4:42 AM, Pavel Velikhov
wrote:
> Hi, is there a paper or a document where one ca
