Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/19082
Sorry for missing the excellent discussions here. After more thoughts, I
feel this patch still makes sense. Currently we have 3 cases that may cause
large method with whole stage codegen:
* a super complex expression. Eventually this would be fixed by #19813
* a complex single operator, e.g. aggregate with 100 aggregate functions.
This is targeted by this PR.
* a complex query. This is targeted by #18931
All of them are orthogonal but non-trivial, I don't see any of them can
cover all other cases.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
