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

Daniel Glöckner edited comment on CALCITE-5227 at 8/30/22 9:18 AM:
-------------------------------------------------------------------

[~julianhyde] the upstream issue in Janino was 
[fixed|https://github.com/janino-compiler/janino/commit/e2ac8b9efa3b22efd01ade45cae35ea3ffb24b35].
 Seems as if they are willing to provide a new Janino release soon. 

Our extensive unit test suite for our Calcite-based code is green again, 
including tests which triggered the earlier Janino bug. 

As this is quite a critical regression for Calcite, could you schedule a new 
release soon?


was (Author: JIRAUSER288949):
[~julianhyde] the upstream issue in Janino was 
[fixed|https://github.com/janino-compiler/janino/commit/e2ac8b9efa3b22efd01ade45cae35ea3ffb24b35].
 Seems as if they are willing to provide a new Janino release soon. As this is 
quite a critical regression for Calcite, could you schedule a new release soon?

> 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)

Reply via email to