Feature/issue 10213 postgres testcontainers

[BrandaoFelipe]

What changes were proposed in this pull request?

Migrate PostgreSQL JDBC integration tests from legacy JdbcPostgresIT to Testcontainers-based tests.

Changes:

• Add PostgresCatalogTest with 9 comprehensive catalog tests
• Add PostgresDialectContainerTest with 13 dialect tests
• Mark JdbcPostgresIT as @Deprecated and @Disabled
• Mark PostgresDialectTests (integration tests) as @Deprecated and @Disabled
• Maintain Java 8 compatibility
• Fix spotless formatting issues
• All 22 tests passing with Testcontainers isolation

Purpose of this pull request

Complete migration of PostgreSQL JDBC tests to Testcontainers as requested in issue #10213. This improves test isolation, reproducibility, and follows modern testing best practices.

Does this PR introduce any user-facing change?

No. This is a test-only change. It does not affect any user-facing functionality, APIs, or documentation.

How was this patch tested?

• All 22 PostgreSQL tests pass locally:
  • PostgresCatalogTest (9 tests)
  • PostgresDialectContainerTest (13 tests)
• Java 8 compatibility verified
• Spotless formatting applied
• Maven build successful: mvn clean compile test -Dtest="*Postgres*"

Check list

• If any new Jar binary package adding in your PR, please add License Notice according
  New License Guide
  → NOT APPLICABLE: No new JARs, only test changes
• If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
  → NOT APPLICABLE: Test-only change, no documentation updates needed
• If necessary, please update incompatible-changes.md to describe the incompatibility caused by this PR.
  → NOT APPLICABLE: No incompatible changes
• If you are contributing the connector code, please check that the following files are updated:
  1. Update plugin-mapping.properties and add new connector information in it
  2. Update the pom file of seatunnel-dist
  3. Add ci label in label-scope-conf
  4. Add e2e testcase in seatunnel-e2e
  5. Update connector plugin_config
     → NOT APPLICABLE: Only test migration, no connector code changes

Additional Notes

• Test parseShouldRemoveQuotesWhenSingleIdentifierIsParsed marked as @Disabled because the parse() method doesn't remove quotes from identifiers (existing behavior)
• Legacy tests kept as deprecated (@Deprecated + @Disabled) for smooth transition
• Follows Testcontainers best practices for database testing

Open Issues Discovered (for follow-up):

1. parse() method doesn't strip quotes from quoted identifiers
2. These are pre-existing behaviors, not regressions from this migration

Closes #10213

[dybyte]

Could you please enable CI according to the instructions and resolve the conflicts?

[chl-wxp]

Why are some class files modified?

[BrandaoFelipe]

Why are some class files modified?

"The target/ files were accidentally committed generated artifacts. I’ve removed them from version control and updated the .gitignore; the PR now only contains source changes.

Regarding the tests, I marked JdbcPostgresIT and PostgresDialectTests as @disabled and @deprecated. Having these new Testcontainers-based tests that cover the same SQL paths, I believe it was redundant to keep these heavy local-DB tests. I'm happy to revert this if the project prefers keeping them enabled."

[chl-wxp]

JdbcPostgresIT should not be closed. The focus of the e2e module and the unit test module are different. The process of the main test tasks of e2e

[BrandaoFelipe]

JdbcPostgresIT should not be closed. The focus of the e2e module and the unit test module are different. The process of the main test tasks of e2e

Hi @chl-wxp, thank you for the feedback. I will restore the JdbcPostgresIT in the E2E module immediately.
Regarding the PostgresDialect tests, I had also disabled them while moving the logic to the new container-based tests. Would you like me to restore those as well to maintain the original coverage, keeping the new tests as a complement?

[chl-wxp]

JdbcPostgresIT should not be closed. The focus of the e2e module and the unit test module are different. The process of the main test tasks of e2e

Hi @chl-wxp, thank you for the feedback. I will restore the JdbcPostgresIT in the E2E module immediately. Regarding the PostgresDialect tests, I had also disabled them while moving the logic to the new container-based tests. Would you like me to restore those as well to maintain the original coverage, keeping the new tests as a complement?

1. I think it is necessary for me to talk about the difference between e2e and unit testing. e2e mainly focuses on submitting seatunnel task process tests, while unit testing focuses on the correctness of internal logic. I mentioned before that I wanted to move the unit tests in the e2e module because the previous code had been written in the wrong location. For example, the unit test in the screenshot below should not appear in e2e.
2. There is no need to delete or close the old unit tests in the connector. You can add or modify them based on the original PostgresDialect unit tests. Our ultimate goal is to successfully automate the test when the completed code is submitted.

[chl-wxp]

JdbcPostgresIT should not be closed. The focus of the e2e module and the unit test module are different. The process of the main test tasks of e2e

Hi @chl-wxp, thank you for the feedback. I will restore the JdbcPostgresIT in the E2E module immediately. Regarding the PostgresDialect tests, I had also disabled them while moving the logic to the new container-based tests. Would you like me to restore those as well to maintain the original coverage, keeping the new tests as a complement?

1. I think it is necessary for me to talk about the difference between e2e and unit testing. e2e mainly focuses on submitting seatunnel task process tests, while unit testing focuses on the correctness of internal logic. I mentioned before that I wanted to move the unit tests in the e2e module because the previous code had been written in the wrong location. For example, the unit test in the screenshot below should not appear in e2e.
2. There is no need to delete or close the old unit tests in the connector. You can add or modify them based on the original PostgresDialect unit tests. Our ultimate goal is to successfully automate the test when the completed code is submitted.

[BrandaoFelipe]

Hi, I noticed the Windows CI is failing because it lacks Docker environment. Wanted to know how do you handle it? Is it renaming the testconteiners with IT.java at the end or using DisabledOnOs(OS.WINDOWS)? I want to sort out this PR, so I can get on with the other databases tests. Thanks! @chl-wxp, @davidzollo.

[chl-wxp]

Hi, I noticed the Windows CI is failing because it lacks Docker environment. Wanted to know how do you handle it? Is it renaming the testconteiners with IT.java at the end or using DisabledOnOs(OS.WINDOWS)? I want to sort out this PR, so I can get on with the other databases tests. Thanks!

using DisabledOnOs(OS.WINDOWS)

[BrandaoFelipe]

Hi, These failing jobs in the CI have something to do with my code or it's all good with the PR? If it's all good, can I be useful in some way? Thank you. @chl-wxp @davidzollo

[chl-wxp]

Hi, These failing jobs in the CI have something to do with my code or it's all good with the PR? If it's all good, can I be useful in some way? Thank you. @chl-wxp @davidzollo

Retry failed ci module