You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pr@cassandra.apache.org by GitBox <gi...@apache.org> on 2023/01/13 12:36:41 UTC

[GitHub] [cassandra-accord] belliottsmith commented on pull request #23: Introduce range transactions, including burn test support for for read-only transactions

belliottsmith commented on PR #23:
URL: https://github.com/apache/cassandra-accord/pull/23#issuecomment-1381794471

   I have added one large follow-up commit that helps support proper range transaction support inside of Cassandra. This required a bit of refactoring so that `calculateDeps` can be asynchronous, as plausibly a large range might require fetching state from disk that could not all readily be held in disk at-once. Also, presently, we don't have any way of knowing what ranges are in-memory and what ranges are not (though we will want to address that in performance work anyway).
   
   Let me know if you would rather spin that addition into a separate patch.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: pr-unsubscribe@cassandra.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: pr-unsubscribe@cassandra.apache.org
For additional commands, e-mail: pr-help@cassandra.apache.org