Use svv_* tables for Redshift metadata queries
#2431
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Redshift supports a concept of external tables. These tables can be queried and insert into, but they are not exposed in the regular `information_schema.tables` metadata. We should instead use `svv_tables` and `svv_columns` to get information about the tables (those views contain information for both external and regular tables).
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Redshift supports a concept of external tables. These tables can be queried and insert into, but they are not exposed in the regular
information_schema.tablesmetadata. We should instead usesvv_tablesandsvv_columnsto get information about the tables (those views contain information for both external and regular tables).This PR is an attempt to add support for external tables to our Redshift implementation. Unfortunately it breaks some of the assumptions in the metadata queries