You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Ruidong Li (JIRA)" <ji...@apache.org> on 2018/10/24 15:39:00 UTC

[jira] [Assigned] (FLINK-8921) Split code generated call expression

     [ https://issues.apache.org/jira/browse/FLINK-8921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ruidong Li reassigned FLINK-8921:
---------------------------------

    Assignee: xueyu  (was: Ruidong Li)

> Split code generated call expression 
> -------------------------------------
>
>                 Key: FLINK-8921
>                 URL: https://issues.apache.org/jira/browse/FLINK-8921
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table API &amp; SQL
>            Reporter: Timo Walther
>            Assignee: xueyu
>            Priority: Major
>              Labels: pull-request-available
>
> In FLINK-8274 we introduced the possibility of splitting the generated code into multiple methods in order to exceed the JVMs maximum method size (see also https://docs.oracle.com/javase/specs/jvms/se7/html/jvms-4.html#jvms-4.9).
> At the moment we only split methods by fields, however, this is not enough in all case. We should also split expressions. I suggest to split the operands of a {{RexCall}} in {{org.apache.flink.table.codegen.CodeGenerator#visitCall}} if we reach a certain threshold. However, this should happen as lazily as possible to keep the runtime overhead low.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)