Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/21568
It's good to cover both of the cases in one design, but I'd like to
prioritize the join one.
I feel it's common to try with different optimization/runtime configs and
make sure we get corrected result. It's more important than the decimal one
that just saves some typing.
Seems it's hard to reach a consensus of a good design to cover both of the
cases, how about we just do the join one? i.e. a SQL test file can specify a
config matrix(we need to design a syntax for it), and the test framework should
run this test file with specified configs and their values to make sure the
results all match the golden file.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
