You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Kent Yao (Jira)" <ji...@apache.org> on 2025/05/06 08:44:00 UTC

[jira] [Updated] (SPARK-51905) Disallow NOT ENFORCED CHECK constraint

     [ https://issues.apache.org/jira/browse/SPARK-51905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kent Yao updated SPARK-51905:
-----------------------------
    Fix Version/s:     (was: 4.1.0)

> Disallow NOT ENFORCED CHECK constraint
> --------------------------------------
>
>                 Key: SPARK-51905
>                 URL: https://issues.apache.org/jira/browse/SPARK-51905
>             Project: Spark
>          Issue Type: Sub-task
>          Components: SQL
>    Affects Versions: 4.1.0
>            Reporter: Gengliang Wang
>            Priority: Major
>              Labels: pull-request-available
>
> As we plan to enforce check constraints by default, it remains unclear what the behavior should be when it is not "enforced".
>  * Option 1: Never support NOVALIDATE/NOT VALID in ALTER TABLE. Use ENFORCED/NOT ENFORCED to check if validation must be done.
>  * Option 2: Start by always doing the validation for CHECK constraints, regardless of ENFORCED/NOT ENFORCED. Add NOVALIDATE/NOT VALID to control this in the future.
>  * Option 3: Don't support of "NOT ENFORCED" for now. Let's think about Option 1 or Option 2 later
>  
> Option3 makes more sense.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org