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

Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2024/10/11 12:04:00 UTC

[jira] [Updated] (FLINK-36474) YAML Table-merging route should accept more type widening cases

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

ASF GitHub Bot updated FLINK-36474:
-----------------------------------
    Labels: pull-request-available  (was: )

> YAML Table-merging route should accept more type widening cases
> ---------------------------------------------------------------
>
>                 Key: FLINK-36474
>                 URL: https://issues.apache.org/jira/browse/FLINK-36474
>             Project: Flink
>          Issue Type: Bug
>          Components: Flink CDC
>            Reporter: yux
>            Priority: Major
>              Labels: pull-request-available
>
> Currently, there are only three specific type widening cases available when performing table-merging routes:
>  * Integer Type Promotions
>  * Float to Double Promotion
>  * Char-like Type to String
> Any other types (including some reasonable ones, like temporal types) will be rejected during wider type inferencing, which is a little surprising, since table-merging route could tolerate columns with various names and counts.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)