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.

Sign up for GitHub

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

Jump to bottom

Bigquery connector: no caching of metadata #10741

Open
grantatspothero opened this issue Jan 21, 2022 · 1 comment
Open

Bigquery connector: no caching of metadata #10741

grantatspothero opened this issue Jan 21, 2022 · 1 comment

Comments

@grantatspothero
Copy link
Contributor

Currently JDBC based connectors have a metadata cache (see this PR: https://github.com/trinodb/trino/pull/2290/files)

However, the bigquery connector is not based on JDBC and thus does not benefit from the metadata caching layer.

Ideally the metadata caching layer implemented here could also be utilized in : #10740

Additionally, when implementing this caching layer make sure to handle cache invalidation (ie: dropping a table through trino should result in SHOW TABLES not returning the dropped table)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ebyhr @grantatspothero