Skip to content

Fix coalesce with nullable union types#6804

Closed
utafrali wants to merge 2 commits intobrimdata:mainfrom
utafrali:fix/issue-6802-sql-vam-coalesce-incorrectly-returns-nul
Closed

Fix coalesce with nullable union types#6804
utafrali wants to merge 2 commits intobrimdata:mainfrom
utafrali:fix/issue-6802-sql-vam-coalesce-incorrectly-returns-nul

Conversation

@utafrali
Copy link
Copy Markdown

@utafrali utafrali commented Apr 7, 2026

Fixes #6802

Coalesce was returning the first non-error vector without checking if it had null values within union types. When it hit a union with null slots, it should've kept looking at other arguments instead. Changed the logic to track which slots are actually null and build merged results from multiple vectors when needed.

@utafrali
Copy link
Copy Markdown
Author

closing this out, feel free to reopen if needed

@utafrali utafrali closed this Apr 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

SQL: vam coalesce incorrectly returns null when value has nullable union type

1 participant