Skip to content

Spark 3.4: Prevent unnecessary failure when executing DML queries with identifier fields - #13448

Merged
stevenzwu merged 5 commits into
apache:mainfrom
szehon-ho:3.4-fix-identifiers
Jul 2, 2025
Merged

stevenzwu merged 5 commits into
apache:mainfrom
szehon-ho:3.4-fix-identifiers

Conversation

@szehon-ho

Copy link
Copy Markdown
Member

Backport of #13435

@github-actions github-actions Bot added the spark label Jul 2, 2025
@szehon-ho szehon-ho added this to the Iceberg 1.10.0 milestone Jul 2, 2025

@amogh-jahagirdar amogh-jahagirdar left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the backport @szehon-ho ! Will merge when checks pass since it's a clean port

@singhpk234 singhpk234 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM as well, Thanks @szehon-ho !

@szehon-ho
szehon-ho force-pushed the 3.4-fix-identifiers branch 2 times, most recently from abd3bde to 3310513 Compare July 2, 2025 20:41
@szehon-ho

Copy link
Copy Markdown
Member Author

Trying to fix the test, it broke as i changed the column to required. Looks like in Spark 3.4 , createDataset defaults to nullable column, which then cannot insert as its incompatbile with required column.

@szehon-ho
szehon-ho force-pushed the 3.4-fix-identifiers branch from 3310513 to 5696df5 Compare July 2, 2025 20:45
@stevenzwu
stevenzwu merged commit b86dc9e into apache:main Jul 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants