Are write-write conflicts possible in Cassandra atomic batches when updating multiple tables?

Hello, The documentation on atomic batches says: "For example, there is no batch isolation. Clients are able to read the first updated rows from the batch, while other rows are still being updated on the server." However does a write-write conflict scenario arise when I'm updating a column in tw

Re: Materialized View: can the view's partition key change due to changes to the underlying table?

Thanks Carl & Jack, that explains it well. The servers does get busy when such an update happens. Very helpful! Will Sent from my iPhone > On 16 Dec 2015, at 00:05, Carl Yeksigian wrote: > > In the case of an update to the source table where data is changed, a > tombstone will be generated f

Re: Usage volume of older versions of Cassandra

Thanks all, I really appreciate the input. On Tue, Dec 15, 2015 at 12:55 PM, Jonathan Haddad wrote: > Yes... I agree with Rob here. I don't see much benchmarking required for > versions of Cassandra that aren't actively supported by the committers. > > On Tue, Dec 15, 2015 at 10:52 AM Robert Co