You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Jark Wu (Jira)" <ji...@apache.org> on 2020/12/30 10:35:00 UTC

[jira] [Commented] (FLINK-20817) kafka source have 798 field,Causes the class to be generated failed

    [ https://issues.apache.org/jira/browse/FLINK-20817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17256439#comment-17256439 ] 

Jark Wu commented on FLINK-20817:
---------------------------------

A workaround would be upgrade to 1.11 where shouldn't contain the SourceConversion node. 
IIRC, Currently we didn't provide code splitting feature for SourceConversion node. 

> kafka source have 798 field,Causes the class to be generated failed
> -------------------------------------------------------------------
>
>                 Key: FLINK-20817
>                 URL: https://issues.apache.org/jira/browse/FLINK-20817
>             Project: Flink
>          Issue Type: Bug
>          Components: Table SQL / API, Table SQL / Planner
>    Affects Versions: 1.10.2
>            Reporter: WeiNan Zhao
>            Priority: Major
>         Attachments: WechatIMG44.jpeg, WechatIMG45.jpeg, WechatIMG46.jpeg
>
>
> Too many fields of flink source cause the generated code to be too long, and a codehaus error is reported.
> Is there a way to bypass this restriction instead of changing your own SQL, because we have many situations where the source table has many fields



--
This message was sent by Atlassian Jira
(v8.3.4#803005)