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

materialize-bigquery: return and error rather than panic if table metadata can't be found #2532

Merged
merged 1 commit into from
Mar 14, 2025

Conversation

williamhbaker
Copy link
Member

@williamhbaker williamhbaker commented Mar 14, 2025

Description:

Although this really shouldn't ever happen, like so many things that shouldn't happen it has happened and the panic is not as useful of an error message as it could be. So we will return a bit more of an instructive error message when it does happen.

Workflow steps:

(How does one use this feature, and how has it changed)

Documentation links affected:

(list any documentation links that you created, or existing ones that you've identified as needing updates, along with a brief description)

Notes for reviewers:

(anything that might help someone review this PR)


This change is Reviewable

…adata can't be found

Although this really shouldn't ever happen, like so many things that shouldn't
happen it has happened and the panic is not as useful of an error message as it
could be. So we will return a bit more of an instructive error message when it
does happen.
@williamhbaker williamhbaker requested a review from mdibaiee March 14, 2025 14:21
@williamhbaker williamhbaker merged commit e4c1051 into main Mar 14, 2025
55 of 59 checks passed
@williamhbaker williamhbaker deleted the wb/bq-partition branch March 14, 2025 14:28
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.

2 participants