-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Fix BigQuery metadata listing for ambiguous table names #18927
Conversation
bee8d94
to
4f740a0
Compare
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.
LGTM % change commit message to Since c9fa5ffe64439cae24070628275d22d1ccbaa897 ....
.
Since c9fa5ff metadata listing does not longer call getTableHandle. Listing columns or tables in BigQuery connector is not failing since for ambiguous tables as they are filtered out.
4f740a0
to
bde96c3
Compare
@hashhar done |
/test-with-secrets sha=bde96c3a4b4d44109649a64801fdeb928113dfde |
The CI workflow run with tests that require additional secrets finished as failure: https://github.com/trinodb/trino/actions/runs/6084072239 |
Damn, closed it by accident. I hope that run with secrets workflow won't be restarted :) |
This particular test that was linked here was successful so I'm merging this change as it-is. |
Since #18730 metadata listing does not longer call getTableHandle so when listing columns or tables in BigQuery connector, ambiguous objects are filtered out.
Fixes #18889 and makes master happy :)
Description
Release notes
(x) This is not user-visible or is docs only, and no release notes are required.