Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/21537
Another example is the AnalysisBarrier, which becomes a disaster to Spark
2.3 release. Many blockers, correctness bugs, performance regressions are
caused by that. Thus, I think we should revert this PR until we have a
high-level design doc and roadmap for the codegen. For example, introducing IR.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
