[
https://issues.apache.org/jira/browse/FLINK-15430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17006039#comment-17006039
]
Jark Wu commented on FLINK-15430:
---------------------------------
Hi [~libenchao], code spliting is not a simple work, I'm not sure whether we
can do it before release.
The community also plans to refactoring code generation in 1.11 for a better
flexible architecture,
also takes code spliting into account. Would be great if you can join the
design together.
So if it is not urgent, I would suggest to postpone it to 1.11.
But I'm also fine to have it before release if you have a simple fixing.
> Fix Java 64K method compiling limitation for blink planner.
> -----------------------------------------------------------
>
> Key: FLINK-15430
> URL: https://issues.apache.org/jira/browse/FLINK-15430
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Planner
> Reporter: Benchao Li
> Priority: Major
>
> Our Flink SQL version is migrated from 1.5 to 1.9, and from legacy planner to
> blink planner. We find that some large SQL meets the problem of code gen
> which exceeds Java 64k method limitation.
> After searching in issues, we find
> https://issues.apache.org/jira/browse/FLINK-8274 which fix the bug to some
> extent. But for blink planner, it has not been fixed for now.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
