[
https://issues.apache.org/jira/browse/CALCITE-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17575399#comment-17575399
]
Julian Hyde commented on CALCITE-5227:
--------------------------------------
Thanks for logging this issue, and thanks for the test case. The workaround is
probably to use the previous version of Janino (3.0.11, I guess). You may be
able to do this with {{-Djanino.version=3.0.11}} on the command line.
I would imagine that this is a high priority issue for Janino and they will
have a fix soon.
I would like to add unit test case in the form of a Calcite query. If we are
pushing Janino's limits then I think we should add tests to Calcite that make
sure that those limits hold.
> Janino upgrade breaks SELECTs with many projects causing JVM crashes
> --------------------------------------------------------------------
>
> Key: CALCITE-5227
> URL: https://issues.apache.org/jira/browse/CALCITE-5227
> Project: Calcite
> Issue Type: Bug
> Affects Versions: 1.30.0
> Reporter: Daniel Glöckner
> Priority: Critical
>
> In our case we have SELECTs with > 1000 project fields. You might say this is
> a bit crazy but this is how our data model looks like ;)
> We recently upgraded to Calcite 1.30 and noticed JVM crashes for such
> SELECTs.
> After thorough analysis we found that the byte code produced by newer Janino
> versions is 350 times larger compared to the byte code produced by javac.
> I created a unit test to reproduce the issue in Calcite code base:
> https://github.com/apache/calcite/commit/f4d4815dff5537c56b34b36794c71d7a9829eec6
> The Janino issue is tracked here:
> https://github.com/janino-compiler/janino/issues/174
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
