GitHub user maropu opened a pull request: https://github.com/apache/spark/pull/19083
[SPARK-21871][SQL] Check actual bytecode size when compiling generated code ## What changes were proposed in this pull request? This pr added code to check actual bytecode size when compiling generated code. In #18810, we added code to give up code compilation and use interpreter execution in `SparkPlan` if the line number of generated functions goes over `maxLinesPerFunction`. But, we already have code to collect metrics for compiled bytecode size in `CodeGenerator` object. So,we could easily reuse the code for this purpose. ## How was this patch tested? Added tests in `WholeStageCodegenSuite`. You can merge this pull request into a Git repository by running: $ git pull https://github.com/maropu/spark SPARK-21871 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/spark/pull/19083.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #19083 ---- commit 65eb028cb501a7e3675710ec72ac773a1700b5f4 Author: Takeshi Yamamuro <yamam...@apache.org> Date: 2017-08-23T13:25:02Z Check compiled byte code size ---- --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- --------------------------------------------------------------------- To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org