feat: Add backtrace feature to simplify enabling native backtraces in CometNativeException

[andygrove]

Which issue does this PR close?

N/A

Rationale for this change

Making life simpler when debugging. We previously asked developers to modify the Cargo.toml file. I just exposed the backtrace feature instead.

What changes are included in this PR?

Expose backtrace feature. Update docs.

How are these changes tested?

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 58.49%. Comparing base (f09f8af) to head (0165dc2).
⚠️ Report is 567 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #2515      +/-   ##
============================================
+ Coverage     56.12%   58.49%   +2.36%     
- Complexity      976     1447     +471     
============================================
  Files           119      146      +27     
  Lines         11743    13550    +1807     
  Branches       2251     2356     +105     
============================================
+ Hits           6591     7926    +1335     
- Misses         4012     4390     +378     
- Partials       1140     1234      +94     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[parthchandra]

FWIW, there is also

datafusion-comet/native/core/src/errors.rs

Line 130 in 07393c1

Panic { msg: String },

which allows us to return a result with a backtrace.

[comphead]

Thanks @andygrove

Its been a while since backtraces introduced in DF and I was thinking to replace Comet errors with DFs? So they would have backtrace capabilities and would be easier to navigate through Comet and DF, WDYT?

[andygrove]

Thanks @andygrove

Its been a while since backtraces introduced in DF and I was thinking to replace Comet errors with DFs? So they would have backtrace capabilities and would be easier to navigate through Comet and DF, WDYT?

I don't know enough about this. Would you mind writing up an issue to explain in more detail?

[comphead]

Thanks @andygrove
Its been a while since backtraces introduced in DF and I was thinking to replace Comet errors with DFs? So they would have backtrace capabilities and would be easier to navigate through Comet and DF, WDYT?

I don't know enough about this. Would you mind writing up an issue to explain in more detail?

DataFusion uses error macros (for example exec_err! wraps ExecutionError) which wraps the error and adds the backtrace if needed. It works in DF to locate approximated root cause.

But what comes to my mind now is: DF backtrace should include Comet entrypoint anyway, because it is caller code, so we don't really need to use error macros in Comet.