SEPURI-SAI-KRISHNA commented on PR #13126: URL: https://github.com/apache/seatunnel/pull/13126#issuecomment-6682668137
@DanielLeens as you asked, #13155 now tracks the Spark hang, so the exclusion in this PR is traceable. One correction to where I was heading. I had been testing a close in `abort()`, but your reviews on #10060 already explain why that is unsafe, and I measured the same effect: JDBC goes from 0 to 2 rows on failure. So the issue proposes ending the JVM after a failed job in local mode instead, which leaves the writer lifecycle and the rows as they are on `dev`. For this PR, [fork run 42075267404](https://github.com/SEPURI-SAI-KRISHNA/seatunnel/actions/runs/42075267404) on `320ac7c6d6` is green. `CassandraIT` ran 20 tests with no failures on both JDKs. In the JDK 11 log, `testCassandra` and the multi-table test ran on 7 engines each, and `testNullPrimaryKeyFailsTheJob` on 5, without Spark. Once this PR and #13156, the fix for #13155, are both merged, I will remove the exclusion. -- 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]
