Re: [DISCUSS] CEP-42: Constraints Framework

Sun, 02 Jun 2024 12:04:40 -0700

Separately, when we discuss benefits of a proposal in a CEP, we should talk about what’s concrete and ignore the stuff that’s idealistic. Of these four points:


This brings to the table several benefits and flexibility. Some examples:

  • Cassandra operators have more control to reason about your data and appropriately tune for performance.
  • Potential reduction on maintenance overhead, being able to better predict partition sizes.
  • Extensibility to more complex validations in the future.
  • Potential value in storage engine making decisions based on data size.
The second is just the first, restated, and the fourth seems incredibly unlikely. The third seems maybe possible, but why not spec out the full range with the CEP instead of assuming iterative implementation?



On Jun 2, 2024, at 20:59, Jeff Jirsa <jji...@gmail.com> wrote:


Would this be implemented solely in the write path? Or would you also try to enforce it in the read and sstable/compaction/repair paths as well?  



On May 31, 2024, at 23:24, Bernardo Botella <conta...@bernardobotella.com> wrote:

Reply via email to