You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Wenchen Fan (Jira)" <ji...@apache.org> on 2025/10/10 11:04:00 UTC
[jira] [Resolved] (SPARK-53786) Default value should not conflict with special column name
[ https://issues.apache.org/jira/browse/SPARK-53786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wenchen Fan resolved SPARK-53786.
---------------------------------
Fix Version/s: 4.1.0
Resolution: Fixed
Issue resolved by pull request 52504
[https://github.com/apache/spark/pull/52504]
> Default value should not conflict with special column name
> ----------------------------------------------------------
>
> Key: SPARK-53786
> URL: https://issues.apache.org/jira/browse/SPARK-53786
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 4.0.0
> Reporter: Szehon Ho
> Assignee: Szehon Ho
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.1.0
>
>
> The following query:
> CREATE TABLE t (current_timestamp DEFAULT current_timestamp)
>
> fails after SPARK-51786. This is because for making default value DSV2 expression, it uses the main analyzer to analyze the default value. However, default value should not know about other columns when trying to analyze.
--
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