Minor: Add backtrace
feature in datafusion-cli
#14997
Merged
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
We can build
datafusion
withbacktrace
feature to display full backtrace when an error is thrown. See https://datafusion.apache.org/user-guide/crate-configuration.html#enable-backtraces.This PR propagates this feature to
datafusion-cli
, when compilingdatafusion-cli
with--features=backtrace
flag, the same feature will be passed to innerdatafusion
crate.What changes are included in this PR?
Add
backtrace
feature todatafusion-cli
build option, and it's only pass through to builddatafusion
.Are these changes tested?
Tested manually.
Without
backtrace
feature:With
backtrace
feature enabled:Are there any user-facing changes?
No