Fix: Show backtrace for ArrowError#17204
Merged
Merged
Conversation
2010YOUY01
commented
Aug 15, 2025
xudong963
approved these changes
Aug 15, 2025
Contributor
|
This PR seems to make |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Which issue does this PR close?
Rationale for this change
When an error is encountered inside DataFusion, the
backtracefeature can be enabled to print the stack trace for the error, for easier debugging.When I was working on a bug fix: I found the backtrace for
ArrowErrormight not be able to display, while most other errors backtrace display is working.See reproducer in
datafusion-cli:Backtrace is displayed for
SchemaErrorBacktrace is not displayed for
ArrowErrorWhat changes are included in this PR?
Show backtrace for
ArrowErrorAre these changes tested?
Added integration test in datafusion-cli
Are there any user-facing changes?
no