[
https://issues.apache.org/jira/browse/CALCITE-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17610515#comment-17610515
]
Daniel Glöckner edited comment on CALCITE-5227 at 9/28/22 11:44 AM:
--------------------------------------------------------------------
[~julianhyde] Good news, our unit test for very wide selects (over 1000
projects) works fine again with Calcite 3.1.8!
With my {{WideTableTest}} in Calcite codebase however, I can only do around 800
projects. We have a complex Calcite adapter for our data model which I cannot
share and it results in different code being generated.
I don't think we need to file a new bug against Janino as the the byte code
from javac also makes the JVM crash.
My proposal would be to change the {{WideTableTest}} so it uses roughly as many
projects as we can currently handle.
was (Author: JIRAUSER288949):
[~julianhyde] Good news, our unit test for very wide selects (over 1000
projects) works fine again with Calcite 3.1.8.
With my {{WideTableTest}} in Calcite codebase however, I can only do around 800
projects. We have a complex Calcite adapter for our data model which I cannot
share and it results in different code being generated.
I don't think we need to file a new bug against Janino as the the byte code
from javac also makes the JVM crash.
My proposal would be to change the {{WideTableTest}} so it uses roughly as many
projects as we can currently handle.
> 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)
