You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@hudi.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/06/01 04:17:00 UTC

[jira] [Updated] (HUDI-4172) Fix the compatibility of flink1.13 when using complex data type.

     [ https://issues.apache.org/jira/browse/HUDI-4172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated HUDI-4172:
---------------------------------
    Labels: pull-request-available  (was: )

> Fix the compatibility of flink1.13 when using complex data type.
> ----------------------------------------------------------------
>
>                 Key: HUDI-4172
>                 URL: https://issues.apache.org/jira/browse/HUDI-4172
>             Project: Apache Hudi
>          Issue Type: Bug
>          Components: flink
>            Reporter: Ying Lin
>            Priority: Major
>              Labels: pull-request-available
>
> Hudi is compatible with `flink1.13` and `flink1.14` in 0.11.0 and provide complex data types.
> But when using `flink-1.13`, there are some class comfilct because of same the fully qualified name in `hudi-flink1.13` and `flink-table-runtime`, so that we cannot provide the guarantee which class the classloader will load.
> For example, `org.apache.flink.table.data.ColumnarMapData` is exists in `hudi-flink1.13` and `flink-table-runtime`, but may flink application's classloader will load the `ColumnarMapData` in `flink-table-runtime`.
> So we need to shade these class with different package when using `flink1.13` profile.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)