-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Possible reproducer of schema metadata bug. #12658
Closed
+6
−10
Closed
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -31,18 +31,14 @@ select * from table_with_metadata; | |
NULL bar | ||
3 baz | ||
|
||
query I rowsort | ||
statement error DataFusion error: Internal error: Physical input schema should be the same as the one converted from logical input schema.. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Check failed with:
|
||
SELECT ( | ||
SELECT id FROM table_with_metadata | ||
) UNION ( | ||
SELECT id FROM table_with_metadata | ||
); | ||
---- | ||
1 | ||
3 | ||
NULL | ||
|
||
query I rowsort | ||
statement error DataFusion error: Internal error: Physical input schema should be the same as the one converted from logical input schema.. | ||
SELECT "data"."id" | ||
FROM | ||
( | ||
|
@@ -54,9 +50,6 @@ FROM | |
SELECT "id" FROM "table_with_metadata" | ||
) as "samples" | ||
WHERE "data"."id" = "samples"."id"; | ||
---- | ||
1 | ||
3 | ||
|
||
statement ok | ||
drop table table_with_metadata; |
Oops, something went wrong.
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.
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.
This change effectively discards the metadata when converting from DFSchema --> Schema (HashMap::new() is empty metadata)
So I am not surprised this can trigger the issue described (as it introduces a bug)
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.
Yeah, this is why I wasn't pushing (other) code yesterday. Knew I was brain fried. Sorry about that.
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.
no worries -- I think we are making progress. I am particularly stoked about the
metadata.slt
idea to try and trigger some of the errors we are seeing (and I think that would make it easier to avoid this kind of regression going forward)