-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Benchmark subcommand to distinguish between DataFusion and Ballista #402
Conversation
Codecov Report
@@ Coverage Diff @@
## master #402 +/- ##
=======================================
Coverage 74.94% 74.94%
=======================================
Files 146 146
Lines 24314 24314
=======================================
+ Hits 18221 18223 +2
+ Misses 6093 6091 -2
Continue to review full report at Codecov.
|
There are two other files which will need updating:
|
Fixed DataFusionBenchmarkOpts name and raspberrypi.md in last commit. |
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.
LGTM. Thanks @jgoday
…pache#402) * apache#401: Add subcommand to TPC-H benchmark args to distinguish between DataFusion and Ballista * fix benchmark subcommand name * Fix lint * fix benchmark tests using DatafusionBenchmarkOpts * Fix DataFusionBenchmarkOpts name and update doc
Which issue does this PR close?
Closes #401.
Rationale for this change
What changes are included in this PR?
It defines a BenchmarkSubCommandOpt to allow different arguments depending on whether it is run against ballista or datafusion.
Are there any user-facing changes?
It changes tpch bin arugments generated by benchmarks project.
It contains changes in benchmarks/README.md and benchmars/run.sh files.