bvolpato opened a new pull request, #37904: URL: https://github.com/apache/beam/pull/37904
## Summary Add a new I/O connector for [Apache Arrow Flight](https://arrow.apache.org/docs/format/Flight.html), enabling high-performance data transfer over gRPC using the Arrow columnar format. Arrow Flight avoids serialization/deserialization overhead and can achieve 10-50x faster data transfer compared to JDBC/ODBC. Fixes #20116 ## Changes - **`ArrowFlightIO.Read`** — BoundedSource-based read transform that fetches Arrow Flight schemas via `getInfo`, splits work by `FlightEndpoint`, and converts record batches to Beam `Row` using the existing `ArrowConversion` extension. - **`ArrowFlightIO.Write`** — DoFn-based write transform that buffers Beam Rows into configurable batches, converts them to Arrow vectors, and streams them to a Flight server via `doPut`. - **Endpoint-level split parallelism** — each `FlightEndpoint` returned by the server becomes a separate sub-source for parallel reads. - **Bearer token authentication** — optional token support via `withToken()`. - **Build integration** — registered `flight-core` and `flight-sql` artifacts in `BeamModulePlugin.groovy`; added the `:sdks:java:io:arrow-flight` module to `settings.gradle.kts`. - **Documentation** — added ArrowFlightIO to `CHANGES.md` (2.73.0) and the built-in connectors table in `connectors.md`. ## Testing Tests use a real in-process `FlightServer` with a `TestFlightProducer`: - **`testRead()`** — starts a Flight server serving two rows, reads them with `ArrowFlightIO.read()`, and asserts the output via `PAssert`. - **`testWrite()`** — writes two rows with `ArrowFlightIO.write()` and verifies the producer received exactly 2 records. Both tests run the full pipeline end-to-end using `TestPipeline` and the DirectRunner. ## Did this cause any problems? Rollback/revert this commit and redeploy the service. ------------------------ Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily: - [x] Mention the appropriate issue in your description (for example: `addresses #123`), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment `fixes #<ISSUE NUMBER>` instead. - [x] Update `CHANGES.md` with noteworthy changes. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). See the [Contributor Guide](https://beam.apache.org/contribute) for more tips on [how to make review process smoother](https://github.com/apache/beam/blob/master/CONTRIBUTING.md#make-the-reviewers-job-easier). To check the build health, please visit [https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md](https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md) GitHub Actions Tests Status (on master branch) ------------------------------------------------------------------------------------------------ [](https://github.com/apache/beam/actions?query=workflow%3A%22Build+python+source+distribution+and+wheels%22+branch%3Amaster+event%3Aschedule) [](https://github.com/apache/beam/actions?query=workflow%3A%22Python+Tests%22+branch%3Amaster+event%3Aschedule) [](https://github.com/apache/beam/actions?query=workflow%3A%22Java+Tests%22+branch%3Amaster+event%3Aschedule) [](https://github.com/apache/beam/actions?query=workflow%3A%22Go+tests%22+branch%3Amaster+event%3Aschedule) See [CI.md](https://github.com/apache/beam/blob/master/CI.md) for more information about GitHub Actions CI or the [workflows README](https://github.com/apache/beam/blob/master/.github/workflows/README.md) to see a list of phrases to trigger workflows. -- 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]
