himanshujindal commented on code in PR #286: URL: https://github.com/apache/cassandra-website/pull/286#discussion_r1946911590
########## site-content/source/modules/ROOT/pages/blog/Introducing-constraints-framework.adoc: ########## @@ -0,0 +1,71 @@ += Upcoming Features: Constraints Framework +:page-layout: single-post +:page-role: blog-post +:page-post-date: February 3, 2025 +:page-post-author: Bernardo Botella Corbi +:description: The Apache Cassandra Community +:keywords: + +Casandra has had limited tools to handle value limits and rules at the time of writing data to a table. Constraints Framework positions itself as the center piece to provide an easy approach to be able to define those rules that gives such flexibility to both Cassandra users and operators by adding a framework to define generic checks at write time. + +Up until now, Cassandra users have relied on limited tools to manage value limits and enforce rules during data writing. Now, with the introduction of the Constraints Framework, Cassandra is able to offer users and operators unprecedented flexibility and control. Here’s everything you need to know about this groundbreaking feature. + +== What is the Constraints Framework? + +The Constraints Framework, introduced through https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-42:+Constraints+Framework[CEP-42,window=_blank], is designed to allow Cassandra users to define rules that validate data at write time. By incorporating these checks, operators can gain: + +* Improved Data Governance: Better control and reasoning about data quality. +* Predictable Performance: Easier tuning for performance and maintenance due to predictable partition sizes. +* Future-Ready Extensibility: The framework lays the groundwork for advanced validations in the future. +* Enhanced Storage Efficiency: Potential for smarter decisions in the storage engine based on data size. + +If you want to know more details, please follow the https://lists.apache.org/thread/xc2phmxgsc7t3y9b23079vbflrhyyywj[dev thread,window=_blank]. + +== What's new? + +Cassandra Query Language (CQL) now includes syntax for defining, altering, and dropping constraints directly within column definitions. Here are some examples: + +---- +CREATE TABLE keyspace.table ( + name text, + i int CHECK (condition) + ..., +); +---- + +Altering Existing Constraints: +---- +ALTER TABLE [IF EXISTS] <table> ALTER [IF EXISTS] <column> CHECK <condition>; +---- +Dropping Constraints: +---- +ALTER TABLE [IF EXISTS] <table> ALTER [IF EXISTS] <column> DROP CHECK; +---- Review Comment: It would be nice if these were actual examples. If we only want to show syntax, we should change the sentence to "Here is the syntax on how to use constraints in CQL:". IMO I would prefer an actual example here, with a link to a CQL doc showing syntax. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
