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.
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
Add
DataFusionError::Collection
to return multipleDataFusionError
s #14439Add
DataFusionError::Collection
to return multipleDataFusionError
s #14439Changes from all commits
184f7e6
ccf36af
1b287ed
ef71a85
8141f23
6ab8b36
4eae829
f642b82
9cd2e12
e2de823
fbe8b5d
5812715
eebf9e8
7b0e7f4
337ea50
28f351a
e3affd7
984d533
451bd71
d10c77b
415029f
b8cf6c9
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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 think you can implement the same thing more simply via
That doesn't handle recursive Collections but I think that is ok
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.
But then in a query like:
You would get one
DataFusionError::Collection
and oneDataFusionError::Plan
whereas you could've gotten threeDataFusionError::Plan
. I think that's worth having thisiter
that's slightly more complicated.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 made a follow on PR to add docs and examples:
DataFusionErrorBuilder
#14551There 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.
💯 for the recursive check
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.
Okay so it turns out that the issue was that the expected error doesn't contain the backtrace but the actual one does. I couldn't reproduce locally at first because I wasn't using the
backtrace
feature.I have no idea why running with
--complete
didn't write the backtrace to the.slt
files, I find no call tostrip_backtrace
and I don't know what in my PR made this necessary. But it works 🤷♂️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 don't think we should add the backtrace to the errors in general (definitely not in
slt
) as the backtraces would include line numbers / call stacks that would change over time.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.
Absolutely. This PR doesn't change that, the backtraces are in the wrapped SchemaError and PlanError. I had to strip them away, don't know why that wasn't necessary before