[
https://issues.apache.org/jira/browse/CALCITE-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17578731#comment-17578731
]
Julian Hyde commented on CALCITE-5227:
--------------------------------------
{quote} The commit is in forked repo. You want it in the main Calcite
repo?{quote}
Actually, the opposite. The URL you supplied,
https://github.com/apache/calcite/commit/f4d4815dff5537c56b34b36794c71d7a9829eec6,
is in the main repo. Your commit happens to be there because of how GitHub
deals with forked repos. But if you were to, say, delete your branch, GitHub
might garbage collect that commit.
If you create a PR, the commit will be around forever.
> 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)
