Run "all schema" JDBC persistence tests on PostreSQL
- Dominant language
- Java
- Stars
- 2.1k
- Forks
- 522
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 140
Description
Following up on https://github.com/apache/polaris/pull/4583#discussion_r3335383203
Currently JDBC schema validation tests run on H2, but it is not considered as the "primary" backend for real world applications. PostgreSQL and CockroachDB are more relevant.
Therefore, schema validations tests should include PostgreSQL and CockroachDB.
H2 can probably be removed from the exhaustive tests and cover only the latest schema version to reduce CI load.
Contributor guide
Research direction
Start by locating the JDBC schema validation tests and their current H2 configuration, then review the discussion in pull request 4583. Determine how the tests run against PostgreSQL and CockroachDB, whether H2 should be limited to the latest schema version, and verify that the resulting CI coverage and load match the issue’s goal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, postgresql
- Domain
- ci-cd, databases, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100