-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Dynamic information_schema configuration and port more tests #4722
Conversation
}; | ||
catalog_list | ||
.register_catalog(config.default_catalog.clone(), default_catalog); | ||
catalog_list.register_catalog( |
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.
The InformationSchema changes are now handed in update_information_schema
3efcfb7
to
936a704
Compare
@@ -30,91 +30,6 @@ use rstest::rstest; | |||
|
|||
use super::*; | |||
|
|||
#[tokio::test] |
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.
I ported a few tests over to show the behavior -- I will port what else I can from this file as a follow on PR
@@ -130,12 +130,6 @@ async fn context_for_test_file(file_name: &str) -> SessionContext { | |||
setup::register_aggregate_tables(&ctx).await; | |||
ctx | |||
} | |||
"information_schema.slt" => { |
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.
since this is now controllable dynamically, we do not have to hard code the sqltest runner
FYI @tustvold |
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.
👍
Benchmark runs are scheduled for baseline = fe3f018 and contender = 34475bb. 34475bb is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
Which issue does this PR close?
Part of #4495
Rationale for this change
Currently the information schema can not be enabled after the
SessionState
is created and it can not be disabled.This means I can't enable it programmatically in the sqllogicttests, and makes for a strange user experience where you can run
set datafusion.catalog.information_schema = true
but it is a noopWhat changes are included in this PR?
information_schema
tests that rely on this behaviorAre these changes tested?
Yes
Are there any user-facing changes?
Users can now enable / disable the information schema
Example: