Repository navigation
feat(trino): append and upsert #78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
32852f5
test(trino): probe MERGE on Iceberg before the upsert relies on it
carolsimone 3b91fa4
refactor(trino): stage helpers shared by every write path
carolsimone c9094df
feat(trino): table_columns from information_schema
carolsimone b03b383
feat(trino): append through a stage table
carolsimone 173877f
feat(trino): ensure_table takes an upsert key and guards format_version
carolsimone aff4d74
feat(trino): upsert through one MERGE from a stage table
carolsimone e335444
fix(trino): import conformance from the testing subpackage
carolsimone File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Low (boundary condition): This guard only fires when the config explicitly sets
format_version. If the target table already exists at Iceberg format v1 (e.g. created before the node became an upsert node) and the config omitsformat_version, the upsert fails later at theMERGEwith a raw Trino error instead of this clearValueError. This mirrors the postgres adapter's deliberate fail-at-ON CONFLICTstance, so it may be intentional — but Trino could cheaply detect it by readingformat_versionfrom{table}$propertieswhen the table already exists and a key is set.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Verified — intentional, and I'm leaving it. The guard is deliberately config-only (documented at
adapter.py:590-594): it rejects an explicitformat_version < 2before any DDL, and otherwise lets the engine reject a live-state mismatch atMERGE. That mirrors the postgres adapter's deliberate fail-at-ON CONFLICTstance for a missing key constraint, so pre-introspecting the live table would make trino stricter than postgres for the same class of problem.The gap you describe is also narrow: modern Trino defaults new Iceberg tables to format v2, so a
MERGEonly hits v1 on areplace→upsertmigration of a table that was explicitly created at v1. A cheap live check is possible here — the adapter already reads"schema"."table$properties"in_table_location— but the exact$propertieskey for the format version isn't something I can verify without the live Trino+Iceberg stack, and shipping a wrong key name would degrade the error (aRuntimeErrorfrom the probe) rather than improve it. If you'd like the clearer error for the migration case, I'll add it as a follow-up with an integration-test case that pins the property key against the real stack.