Improve or remove replicate-on-write setting
--------------------------------------------
Key: CASSANDRA-2397
URL: https://issues.apache.org/jira/browse/CASSANDRA-2397
Project: Cassandra
Issue Type: Bug
Reporter: Stu Hood
The replicate on write setting breaks assumptions in various places in the
codebase dealing with whether data will be replicated in a timely fashion. It's
worthwhile to discuss whether we should go all-the-way on replicate-on-write,
such that it is a fully supported feature, or whether we should remove it
entirely.
On one hand, ROW could be considered to be just another replication tunable
like HH, RR and AES. On the other hand, a lazily replicating store is very
rarely what you actually wanted.
Open issues related to ROW are linked, but additionally, we'd need to:
* Make the setting have an effect for standard column families
* Change the default for ROW to enabled and properly warn of the effects
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
