Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/21677
Yes. @cloud-fan . We can embrace that concept to all the other main-method
style benchmark. Previously, we do the manual copy&paste to put the result into
the nearest place to the corresponding BM code. It's not an easy way for
automation.
With @wangyum 's that specific contribution, we can automate all
benchmarks. Possibly, we can use that in the release process, too. So, are you
heading `main-method` style with separate BM output files? For me, +1.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
