[
https://issues.apache.org/jira/browse/FLINK-16023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17036011#comment-17036011
]
Jark Wu edited comment on FLINK-16023 at 2/13/20 8:16 AM:
----------------------------------------------------------
Btw, it's not always possible to use the kafka topic as the registered table
name, because Kafka topic can use dash, however, dash is not allowed as an
indentifier in SQL. That means a "log-events" topic, may should be registered
as "log_events" table.
was (Author: jark):
Btw, it's not always possible to use the kafka topic as the registered table
name, because Kafka topic can use dash(-), however, dash(-) is not allowed as
an indentifier in SQL. That means a "log-events" topic, may should be
registered as "log_events" table.
> 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)
