Hi everyone,

After Constraints framework was merged in, I would like to come back to the 
discussion Jordan brought up in this Jira:
https://issues.apache.org/jira/browse/CASSANDRA-19677

For context, that Jira ticket (and PR) is adding a bunch of more fine grained 
size thresholds for column types using guardrails, expanding on what these 
Jiras added:
https://issues.apache.org/jira/browse/CASSANDRA-17151
https://issues.apache.org/jira/browse/CASSANDRA-17150

Now, we have an alternative way to set sizes to scpecific columns using 
constraints (we have LENGHT constraint, which is technically different, but 
adding a SIZE constraint is on the roadmap and straight forward).

Jordan raised a really valid concern that these new guardrails may be adding 
some noise to an already crowded space such as settings. On the other hand, 
these guardrails operate at a different level than constraints, as they are 
generic as opposed to column specific.

We would like to hear what the community think in this case. Should these 
guardrails go in? Or do we drop them in favour of plain constraints?

My two cents: My opinion is that these guardails still add value and help 
operators a more fine grained control to "protect" the database.

Regards,
Bernardo

Reply via email to