Fix staging table strategy#249
Merged
Merged
Conversation
sgrebnov
approved these changes
May 22, 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.
🗣 Description
Got broken in #243
The staging table strategy strips primary keys from dataset configs to prevent Cayenne's upsert-on-conflict behavior from conflicting with MERGE-based updates. However, the stripping happened before
setup()was called, so the system adapter also received empty PKs — breaking Lakebase'screate_synced_tableAPI which requires at least one primary key column.Fix: clone datasets before stripping so setup gets the original PKs, while the ETL pipeline still gets the stripped version.
Verified in https://github.com/spiceai/spicebench/actions/runs/25971199591