Added a comment about "ACID". I would recommend not saying ACID until it's there. C* has strong consistency when needed. It doesn't for example guarantee that two competing mutations will be executed (or be able to be rolled back to the previous state) in the same exact order they were intended if they come in at the same time, especially if these are coming from two different data centers for example.
Maybe it can be explained later that the commitlog mechanism provides ACID-like features ... ? >From my understanding the Accord white paper has not been implemented into any working Cassandra code. I may be wrong. Rahul Singh Chief Executive Officer | Business Platform Architect m: 202.905.2818 e: rahul.si...@anant.us li: http://linkedin.com/in/xingh ca: http://calendly.com/xingh *We create, support, and manage real-time global data & analytics platforms for the modern enterprise.* *Anant | https://anant.us <https://anant.us/>* 3 Washington Circle, Suite 301 Washington, D.C. 20037 *http://Cassandra.Link <http://cassandra.link/>* : The best resources for Apache Cassandra On Tue, Aug 23, 2022 at 5:43 AM Sharan Foga <sha...@apache.org> wrote: > Hi Chris > > I've added a few comments and suggestions. Please feel free to use /ignore > whichever ones you think :-) > > Thanks > Sharan > > On 2022/08/23 00:08:52 Chris Thornett wrote: > > Opening up Alex Sorokoumov's guide 'Learn How CommitLog Works in Apache > > Cassandra' for a 72-hr community review by lazy consensus. > > > > Please add any amends and suggestions in the comments: > > > https://docs.google.com/document/d/1cyOi-IeU_I9GBkpQbJS6IIrmemAesEqvzLb-eeFs_rM/edit# > > > > Thanks! > > > > -- > > > > Chris Thornett > > Senior Content Strategist, Constantia.io > > >
