You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Timo Walther (Jira)" <ji...@apache.org> on 2021/10/20 08:19:00 UTC

[jira] [Closed] (FLINK-24397) Reduce legacy in Table API connectors

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

Timo Walther closed FLINK-24397.
--------------------------------
    Fix Version/s: 1.15.0
     Release Note: The old JDBC connector (indicated by `connector.type=jdbc` in DDL) has been removed. If not done already, users need to upgrade to the newer stack (indicated by `connector=jdbc` in DDL).
       Resolution: Fixed

Fixed in master:

commit 66d9188a368dc02aa36255523c6ba7a7d3847f82
[connectors/jdbc] Cleanup the Jdbc table connector by removing legacy

commit cd209bd547a9db4d30817d61f3b80a9323451506
[connectors/hbase] Remove TableSchema usage from Hbase table connector

commit ffc0c9734c44e96f1d490a8364b025a8621d0bfa
[connectors/kafka] Remove TableSchema usage from Kafka table connector

> Reduce legacy in Table API connectors
> -------------------------------------
>
>                 Key: FLINK-24397
>                 URL: https://issues.apache.org/jira/browse/FLINK-24397
>             Project: Flink
>          Issue Type: Improvement
>          Components: Connectors / Common, Table SQL / API
>    Affects Versions: 1.15.0
>            Reporter: Fabian Paul
>            Assignee: Fabian Paul
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.15.0
>
>
> The TableSchema class is now deprecated for a while but a lot of connectors still depend on it use (DynamicTableSources and DynamicTableSinks). We should reduce the usage of the TableSchema to provide a better example for external contributions and allow us eventually to drop the TableSchema.
> It also drops the legacy JDBC connector.



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