[
https://issues.apache.org/jira/browse/FLINK-16023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17035919#comment-17035919
]
Bowen Li commented on FLINK-16023:
----------------------------------
[~jark] 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.
this is not specific to jdbc, but general to kafka and hbase sql connector as
well. I just created FLINK-16027 and FLINK-16028 to track them
> 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
> Assignee: Jingsong Lee
> Priority: Major
> Fix For: 1.11.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.3.4#803005)
