apache/seatunnel

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

Open

#10210 opened on Dec 18, 2025

View on GitHub
 (3 comments) (1 reaction) (0 assignees)Java (6,897 stars) (1,432 forks)batch import
good first issuehelp wanted

Description

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

Contributor guide

Tech stack
javasqlmysqlpostgresqldocker
Domain
testingbackend
Issue type
test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaJDBCUnit testingDocker
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
The issue aims to improve unit testing for JDBC connectors in Apache SeaTunnel (issue #10210). The first step is to introduce Docker containers for each database (mysql, oracle, pgsql, sqlserver, dameng, db2, kingbase) so that tests can run in CI. Then, add unit tests for jdbcCatalog and jdbcDialect, including boundary conditions. Finally, move relevant tests from the jdbc e2e module to connector jdbc. The implementation scope table shows databases with no current assignees, so contributors can pick one to start.