[
https://issues.apache.org/jira/browse/CALCITE-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17601400#comment-17601400
]
Julian Hyde commented on CALCITE-5227:
--------------------------------------
[dynamicRowTypeTable|https://github.com/apache/calcite/blob/d1cf4a38b71b514b1d208b5ffa3220b92693464f/testkit/src/main/java/org/apache/calcite/util/Smalls.java#L389]
is that kind of table. It is currently only used in validator and interpreter
tests but could be used in tests that generate and execute Java plans. Let me
know if you need help. If you can produce a PR in 24 hours we can get it into
the next release. I can't go into the reasons for the quick release schedule.
> 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
> Fix For: 1.32.0
>
>
> 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)
