Repository navigation
fix(starrocks): don't default column names for multi-array UNNEST - #8671
Merged
Merged
Conversation
…AUDE] StarRocks names every column of a multi-array UNNEST "unnest", but sqlglot added the single-column alias AS unnest(unnest), which StarRocks rejects with "table unnest has 2 columns available but 1 columns specified". The default column name is now only added for a single array.
georgesittas
approved these changes
Oct 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
A StarRocks
UNNESTwith several arrays and no column names was generated with a single-column alias, which StarRocks rejects:Solution
Only add the default
unnestcolumn name for a single array. StarRocks names every column of a multi-arrayUNNESTunnest, so no column list matches it, and the table alias alone keeps the statement valid.