Hello,
I want to understand the community's thoughts on using newer features (post
JDK11) in upcoming releases in Cassandra. An example is flow scoping
instead of explicitly casting types with instanceOf:
https://openjdk.org/jeps/395. I want your thoughts on JDK requirements for
the main Cassandra
Setting aside the paxos vs accord conversation (though admittedly my first question would have been “why not accord”), I’m curious from folks who have thought about this how you’re thinking about correctness of repairI ask because I have seen far more data resurrection cases than I have lost write
Here’s my perspective:
#1 Accord vs. LWT round trips
Based on the insights shared by the Accord experts, it appears that
implementing MV using Accord can achieve a comparable number of round trips
as the LWT solution proposed in CEP-48. Additionally, it seems that the
number of WAN RTTs might be
Based on David and Blake’s responses, it sounds like we don’t need to block
on anything.
I realize you may be making a broader point, but in this instance it sounds
like there’s nothing here preventing an accord based MV implementation. Now
that i understand more about how it would be done, it als
> IMHO, focus should be on accord-based MVs. Even if that means it's blocked
> on first adding support for multiple conditions.
>
Strongly disagree here. We should develop features to be as loosely coupled
w/one another as possible w/an eye towards future compatibility and leverage
but not blo
> Curious what others think though. I'm +1 on the spirit of getting MVs to
> a stable point, but not convinced this is the best approach.
>
IMHO, focus should be on accord-based MVs. Even if that means it's blocked
on first adding support for multiple conditions.
