You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yun Gao (Jira)" <ji...@apache.org> on 2022/04/13 06:28:04 UTC
[jira] [Updated] (FLINK-16023) jdbc connector's 'connector.table' property should be optional rather than required
[ https://issues.apache.org/jira/browse/FLINK-16023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yun Gao updated FLINK-16023:
----------------------------
Fix Version/s: 1.16.0
> jdbc connector's 'connector.table' property should be optional rather than required
> -----------------------------------------------------------------------------------
>
> Key: FLINK-16023
> URL: https://issues.apache.org/jira/browse/FLINK-16023
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / JDBC
> Reporter: Bowen Li
> Priority: Minor
> Labels: auto-deprioritized-major
> Fix For: 1.15.0, 1.16.0
>
>
> jdbc connector's 'connector.table' property should be optional rather than required.
> connector should assume the table name in dbms is the same as that in Flink when this property is not present
> The fundamental reason is that such a design didn't consider integration with catalogs. Once introduced catalog, the flink table's name should be just the 'table''s name in corresponding external system.
> cc [~ykt836]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)