[
https://issues.apache.org/jira/browse/FLINK-15430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benchao Li updated FLINK-15430:
-------------------------------
Description:
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.
was:
Our SQL 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.
> 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)
