[jira] [Commented] (CALCITE-5227) Janino upgrade breaks SELECTs with many projects causing JVM crashes

["Julian Hyde (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CALCITE-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17611986#comment-17611986 ] 

Julian Hyde commented on CALCITE-5227:
--------------------------------------

That's good news. Thanks for letting me know.

Please be sure to also let Arno know over at Janino. His support has been exemplary.

Please submit a PR for the test changes and nag me in this JIRA case until it is merged. I'll mark this case fixed when the test case is merged.

> 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
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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)