[ 
https://issues.apache.org/jira/browse/FLINK-40244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18099653#comment-18099653
 ] 

Linsert commented on FLINK-40244:
---------------------------------

I’d like to take on this task and submit a PR for YashanDB support. Could you 
please assign this issue to me? Thanks!

> Support YashanDB in flink-connector-jdbc
> ----------------------------------------
>
>                 Key: FLINK-40244
>                 URL: https://issues.apache.org/jira/browse/FLINK-40244
>             Project: Flink
>          Issue Type: New Feature
>          Components: Connectors / JDBC
>            Reporter: Linsert
>            Priority: Minor
>
> h4. Feature Description
> YashanDB is an enterprise-grade relational database management system widely 
> used in various business scenarios. Currently, `flink-connector-jdbc` 
> provides submodules and dialects for various databases (such as MySQL, 
> PostgreSQL, OceanBase, Oracle, etc.), but lacks dialect support for 
> YashanDB.[yashandb official website|https://www.yashandb.com/]
> Adding YashanDB dialect support will enable users to read from and write to 
> YashanDB efficiently using Flink JDBC connector.
> h5. Proposed Changes
>  # Create a new module/package `flink-connector-jdbc-yashandb` (or add 
> `YashanDBDialect` inside the existing dialect architecture).
>  # Implement `YashanDBDialect` extending `AbstractDialect`:  - Define type 
> mappings between YashanDB and Flink logical types.  - Implement SQL syntax 
> generators (such as Upsert/Merge syntax, Quotes, Identifier validation, 
> Limit/Offset pagination if applicable).
>  # Add `YashanDBCatalog` (optional / if needed for Flink SQL catalog support).
>  # Add unit tests and integration tests for YashanDB dialect.
> h5. Additional Context
>  * Driver class: `com.yashandb.jdbc.Driver` (or relevant driver)
>  * I am willing to submit a PR for this feature if agreed by the community.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to