apache / apache/polaris

JDBC testing against multiple isolation levels

Open
#2,263 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Java
Stars
2.1k
Forks
522
Avg merge
1d 22h
Merged PRs (30d)
137

Description

### Is your feature request related to a problem? Please describe.

The change #2219 has been created to fix an NPE that happens when JDBC is used with _serializable_ isolation level.

We need a thorough, JDBC oriented, set of tests that exercise against various isolation levels (read-commtted & serializable) against H2 _and_ Postgres. The tests should not only cover the case of #2219 but more generally "all" scenarios, including "interleaved" concurrent changes.

### Describe the solution you'd like

_No response_

### Describe alternatives you've considered

_No response_

### Additional context

_No response_

Contributor guide

Open the contributing guide

Research direction

Read change #2219 first, then locate the existing JDBC tests and determine how they exercise isolation levels on H2 and Postgres. Done means a thorough test set covering read-committed and serializable isolation, including the #2219 case and interleaved concurrent changes.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, postgres
Domain
databases, testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.