davidzollo opened a new pull request, #11929: URL: https://github.com/apache/seatunnel/pull/11929
## Purpose Replacement for #10958 on an Apache-owned maintainer branch so current-head CI can run from the main repository. This republishes the Arrow reader fix line from the current `#10958` head onto `apache/seatunnel` and keeps only the functional commits: - `[Fix][Connector-V2] Fix Arrow memory leak by correcting close order in ArrowToSeatunnelRowReader` - `[Fix][Connector-V2] Ensure Arrow allocator closes on reader failure` The republish intentionally excludes unrelated CI-refresh and documentation-only commits from the contributor branch. ## Why this replacement PR exists The original open PR #10958 currently points at `davidzollo/seatunnel`. For this release batch we need the fix to run on an Apache-owned branch instead of continuing on a fork branch. ## Source scope This patch stays limited to the two files already changed on the original PR head: - `seatunnel-connectors-v2/connector-common/src/main/java/org/apache/seatunnel/connectors/seatunnel/common/source/arrow/reader/ArrowToSeatunnelRowReader.java` - `seatunnel-connectors-v2/connector-common/src/test/java/org/apache/seatunnel/connectors/seatunnel/common/source/arrow/reader/ArrowToSeatunnelRowReaderCloseTest.java` ## Current-head CI note The latest failed CI on the original PR is not in this patch scope: it fails in `seatunnel-engine-server` on the Windows `unit-test` shard, while this fix only touches `connector-common` Arrow reader code and its dedicated regression test. ## Validation Per the current SeaTunnel maintainer workflow for this batch, local validation was formatting-only: - `./mvnw spotless:apply -pl seatunnel-connectors-v2/connector-common -am -nsu` - `git diff --check` GitHub CI on this Apache-owned branch is the source of truth for compile, test, and runtime validation. -- 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]
