2010YOUY01 opened a new pull request, #16236:
URL: https://github.com/apache/datafusion/pull/16236
## Which issue does this PR close?
<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases. You can
link an issue to this PR using the GitHub syntax. For example `Closes #123`
indicates that this PR will close issue #123.
-->
- Closes #.
## Rationale for this change
<!--
Why are you proposing this change? If this is already explained clearly in
the issue then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand your
changes and offer better suggestions for fixes.
-->
Before, the debug `cargo` command would only be printed when running `tpch`
benchmark with `bench.sh` script (see the last line)
```sh
yongting@Mac ~/C/d/benchmarks (main>) [SIGINT]> ./bench.sh run tpch
***************************
DataFusion Benchmark Script
COMMAND: run
BENCHMARK: tpch
DATAFUSION_DIR: /Users/yongting/Code/datafusion/benchmarks/..
BRANCH_NAME: main
DATA_DIR: /Users/yongting/Code/datafusion/benchmarks/data
RESULTS_DIR: /Users/yongting/Code/datafusion/benchmarks/results/main
CARGO_COMMAND: cargo run --release
PREFER_HASH_JOIN: true
***************************
RESULTS_FILE:
/Users/yongting/Code/datafusion/benchmarks/results/main/tpch_sf1.json
Running tpch benchmark...
+ cargo run --release --bin tpch -- benchmark datafusion --iterations 5
--path /Users/yongting/Code/datafusion/benchmarks/data/tpch_sf1
--prefer_hash_join true --format parquet -o
/Users/yongting/Code/datafusion/benchmarks/results/main/tpch_sf1.json
```
This debug print is helpful if we want to override some default options.
This PR adds this debug print to all existing benchmarks.
## What changes are included in this PR?
<!--
There is no need to duplicate the description in the issue here but it is
sometimes worth providing a summary of the individual changes in this PR.
-->
## Are these changes tested?
<!--
We typically require tests for all PRs in order to:
1. Prevent the code from being accidentally broken by subsequent changes
2. Serve as another way to document the expected behavior of the code
If tests are not included in your PR, please explain why (for example, are
they covered by existing tests)?
-->
I tested it manually.
## Are there any user-facing changes?
<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->
<!--
If there are any breaking changes to public APIs, please add the `api
change` label.
-->
No
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org
For additional commands, e-mail: github-h...@datafusion.apache.org
