apache/seatunnel

[Feature][connector-jdbc] Optimize unit testing of jdbc connector code

Open

#10.210 aperta il 18 dic 2025

Vedi su GitHub
 (3 commenti) (1 reazione) (0 assegnatari)Java (1432 fork)batch import
good first issuehelp wanted

Metriche repository

Star
 (6897 star)
Metriche merge PR
 (Merge medio 13g 21h) (143 PR mergiate in 30 g)

Descrizione

Search before asking

  • I had searched in the feature and found no similar feature requirement.

Description

Problem

  1. At present, the unit tests of connector-jdbc code basically rely on the local environment and will be turned off during the actual running of ci, which will lead to functional risks. We hope to introduce docker containers and run unit tests in the actual ci process.
  2. The unit test coverage of connector-jdbc code is relatively low, such as the jdbcCatalog test and jdbcDialect test. Additionally, there is a lack of boundary condition test cases. We hope to add relevant test cases.
  3. After completing points 1 and 2, you can transfer the unit tests in the jdbc-e2e module to connector-jdbc.

Implementation scope

type status Assignees
mysql
oracle
pgsql
sqlserver
dameng
db2
kingbase

Usage Scenario

No response

Related issues

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Guida contributor