Skip to content
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

BigQuery: Skip merge if no primary keys present #1290

Merged
merged 6 commits into from
Feb 14, 2024

Conversation

Amogh-Bharadwaj
Copy link
Contributor

Merge statements currently are syntactically incorrect for tables without a primary key. This case is ideally not seen as tables without pkey/replica identity full are filtered out the UI level but in branches where we rely on signals for adding tables, this case can go unchecked and normalize flow fails.

This PR skips a table during merge if there are no primary keys for it.

@Amogh-Bharadwaj Amogh-Bharadwaj merged commit 51f4256 into customer-ak Feb 14, 2024
2 of 3 checks passed
@Amogh-Bharadwaj Amogh-Bharadwaj deleted the hack/no-pkey-skip-merge branch February 14, 2024 14:04
Amogh-Bharadwaj added a commit that referenced this pull request Feb 14, 2024
Merge statements currently are syntactically incorrect for tables
without a primary key. This case is ideally not seen as tables without
pkey/replica identity full are filtered out the UI level but in branches
where we rely on signals for adding tables, this case can go unchecked
and normalize flow fails.

This PR skips a table during merge if there are no primary keys for it.
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.

1 participant