[
https://issues.apache.org/jira/browse/FLINK-8274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16381647#comment-16381647
]
ASF GitHub Bot commented on FLINK-8274:
---------------------------------------
Github user twalthr commented on the issue:
https://github.com/apache/flink/pull/5174
@Xpray Yes, I think for a long term solution we should move some variables
in the member area but I don't know if it makes sense to move all local
variables there. We should fix the `expandLocalRef` thing and put all local
references to the member area if you mean that?
> Fix Java 64K method compiling limitation for CommonCalc
> -------------------------------------------------------
>
> Key: FLINK-8274
> URL: https://issues.apache.org/jira/browse/FLINK-8274
> Project: Flink
> Issue Type: Bug
> Components: Table API & SQL
> Affects Versions: 1.5.0
> Reporter: Ruidong Li
> Assignee: Ruidong Li
> Priority: Critical
>
> For complex SQL Queries, the generated code for {code}DataStreamCalc{code},
> {code}DataSetCalc{code} may exceed Java's method length limitation 64kb.
>
> This issue will split long method to several sub method calls.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
