-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Use show schemas
instead of selecting from information_schema.schemata on Snowflake
#2166
Labels
Comments
The big drawback of |
4 tasks
beckjake
added a commit
that referenced
this issue
Mar 3, 2020
…emas-snowflake use show schemas for snowflake list_schemas (#2166)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the feature
Background:
Let's replace the call to
information_schema.schemata
on Snowflake with a call toshow schemas in <database>
.Advantages:
show schemas
will not queue, whereas theselect
statement can queueshow schemas
does not require a running warehouseshow schemas
appears to be strictly faster than the information_schema alternativeWe should consider applying this approach for other queries, as described in #1877 (the key benefit being that these queries do not queue. Let's keep #1877 open and tackle these other queries separately. See also #2157
Disadvantages:
show schemas
requires the database name to be cased and quoted appropriately. I actually think this is the same behavior as selecting fromdatabase.information_schema.<table>
, so that might not be an issue here?The text was updated successfully, but these errors were encountered: