[
https://issues.apache.org/jira/browse/FLINK-34572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rui Fan resolved FLINK-34572.
-----------------------------
Fix Version/s: jdbc-3.3.0
Assignee: He Wang
Resolution: Fixed
> JDBC: Support OceanBase catalog
> -------------------------------
>
> Key: FLINK-34572
> URL: https://issues.apache.org/jira/browse/FLINK-34572
> Project: Flink
> Issue Type: New Feature
> Components: Connectors / JDBC
> Reporter: He Wang
> Assignee: He Wang
> Priority: Major
> Labels: pull-request-available
> Fix For: jdbc-3.3.0
>
>
> As the OceanBase dialect has been introduced, we can support the OceanBase
> catalog in jdbc connector now.
> - The catalog of OceanBase MySQL mode should be same with MySQL catalog
> except 'builtinDatabases'.
> - In OceanBase Oracle mode, there is no 'database' but 'schema', which is
> corresponded to the user name. As there is no Oracle catalog for now, I'm not
> sure how should we use 'database' and 'schema' in the catalog. Personally, I
> prefer to use 'schema' as 'database'.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
