Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/19813
Do we have to sacrifice one of them? If we do then I agree deeply nested
expression is more common than a long chain of arithmetic expressions and we
should get this patch. I think we should explore more about how to split
methods in whole stage codegen before making this decision, at least now I'm
not convinced that we have to forbid expressions to output statement.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
