[
https://issues.apache.org/jira/browse/SPARK-51905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated SPARK-51905:
-----------------------------------
Labels: pull-request-available (was: )
> 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
> Assignee: 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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
