Open grantatspothero opened 2 years ago
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 : https://github.com/trinodb/trino/issues/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)
SHOW TABLES
Relates to #4580
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 : https://github.com/trinodb/trino/issues/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)