[
https://issues.apache.org/jira/browse/FLINK-8274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16383631#comment-16383631
]
ASF GitHub Bot commented on FLINK-8274:
---------------------------------------
Github user twalthr commented on the issue:
https://github.com/apache/flink/pull/5613
@Xpray yes that might be necessary as well. I think this code does not
solve all problems but the most urgent ones. It still fails if expressions in a
field become too large or the unboxing. Or even the class itself. There are
many limitation that could be reached:
https://docs.oracle.com/javase/specs/jvms/se7/html/jvms-4.html#jvms-4.9
Do you have use cases where you reach the limits with my current
implementation?
> 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)
