apache/seatunnel

[Feature][connector-jdbc][oracle] Optimize unit testing for Oracle in JDBC connector

Open

#10212 opened on Dec 18, 2025

View on GitHub
 (1 comment) (0 reactions) (1 assignee)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

This issue focuses on improving and expanding unit test coverage for the Oracle case in the connector-jdbc module, consistent with the scope defined in #10210.

  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.

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