Repository navigation
fix: Trino union selects - #465
Merged
Merged
Conversation
Since Trino 482, the `lower_bounds` and `upper_bounds` columns of the `$files` metadata table changed from `map(integer, varchar)` to typed `row` values. This broke the union which requires the fields from the first select to match names and types for any union selects. Co-authored-by: Techassi <git@techassi.dev>
Since Trino 482, the `lower_bounds` and `upper_bounds` columns of the `$files` metadata table changed from `map(integer, varchar)` to typed `row` values. This broke the union which requires the fields from the first select to match names and types for any union selects. Co-authored-by: Techassi <git@techassi.dev>
Maleware
approved these changes
Oct 14, 2026
Maleware
left a comment
Member
There was a problem hiding this comment.
Thanks for getting that! LGTM :)
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
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.
Since Trino 482, the
lower_boundsandupper_boundscolumns of the$filesmetadata table changed frommap(integer, varchar)to typedrowvalues.This broke the union which requires the fields from the first select to
match names and types for any union selects.
Upstream change PR: trinodb/trino#28997