laughingman7743 commented on PR #156:
URL:
https://github.com/apache/flink-connector-jdbc/pull/156#issuecomment-3566844266
## CI Failure Investigation
I investigated the CI failure in the `compile_and_test (2.1.1, 17)` job and
found the following:
### Error Details
**Failed Test:**
`JdbcSourceITCase.testReadWithoutParallelismWithParamsProvider`
**Root Cause Exception:**
```
java.sql.SQLNonTransientConnectionException: No current connection.
at
org.apache.flink.connector.jdbc.core.datastream.source.reader.JdbcSourceSplitReader.openResultSetForSplitWhenAtLeastOnce
at
org.apache.flink.connector.jdbc.core.datastream.source.reader.JdbcSourceSplitReader.openResultSetForSplitWhenAtMostOnce
at
org.apache.flink.connector.jdbc.core.datastream.source.reader.JdbcSourceSplitReader.openResultSetForSplit
```
### Analysis
1. **Not Spanner-specific**: This failure occurs in the
`flink-connector-jdbc-core` module's test, not in Spanner-specific code.
2. **Derby JDBC Connection Issue**: The Derby JDBC connection is being
closed unexpectedly during ResultSet processing.
3. **Branch Status**: This branch is already up-to-date with the latest main
branch (commit 669314d), including recent hotfixes:
- 669314d: Apply the correct version matrix in weekly CI
- 45cbf78: Change Flink matrix to resolve Flink correctly (#179)
4. **Recent main branch CI**: The main branch CI has been passing after
these hotfixes.
### Local Test Results
I ran the same test locally with both Flink versions:
**Flink 2.1.1:**
```
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.255
s
[INFO] BUILD SUCCESS
```
**Flink 2.0.1:**
```
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.325
s
[INFO] BUILD SUCCESS
```
Both tests passed successfully in the local environment.
### Conclusion
This appears to be a **CI environment-specific issue** rather than a code
problem:
- The test passes locally with both Flink 2.1.1 and 2.0.1
- The issue is in `flink-connector-jdbc-core`, not Spanner-specific code
- May be related to timing, resource constraints, or containerization in the
CI environment
### Recommendation
- Re-run the CI to see if it's a transient issue
- This failure should not block the Spanner dialect PR as it's unrelated to
the Spanner implementation
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
