-
Notifications
You must be signed in to change notification settings - Fork 360
feat: Support configuring datafusion catalog in sqllogictest framework #1865
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
base: main
Are you sure you want to change the base?
Conversation
|
Hi @kaori-seasons this pr contains a lot of unrelated changes, please fix format first. |
Hello @liurenjie1024 , these seemingly unrelated changes were caused by my local use of cargo fmt, and I'm fixing them. |
|
Hi @kaori-seasons, thanks for helping out! My original intention of the issue is to keep it simple for the first version of sql logic test framework and iterate from there. and we don't need to specify which engine uses which catalog to keep things simpler (I think most test scenarios just needs one shared catalog). |
| /// Format AWS SDK error into iceberg error | ||
| pub(crate) fn from_aws_sdk_error<T>(error: aws_sdk_glue::error::SdkError<T>) -> Error | ||
| where T: Debug { | ||
| where |
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.
Why this change?
| "my_table".to_string() | ||
| )]); | ||
| assert_eq!( | ||
| result, |
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.
There are many format related changes, it's better to avoid that.
Which issue does this PR close?
Related to issue-1780
What changes are included in this PR?
Are these changes tested?