ATHARVA262005 opened a new pull request, #37411:
URL: https://github.com/apache/beam/pull/37411

   ## Description
   This PR addresses a scalability bottleneck in `SparkReceiverIO` where data 
reading was previously restricted to a single worker.
   
   Previously, the `Read` transform used `Impulse.create()`, which limited the 
downstream `Splittable DoFn` execution to a single initial restriction. This 
change introduces proper parallelization logic, allowing users to configure 
multiple concurrent readers.
   
   ### Key Changes:
   - **Added `withNumReaders(int)`**: A new configuration option to the 
`SparkReceiverIO` builder.
   - **Parallel Work Distribution**: Implemented `Create.of(shards)` + 
`Reshuffle` pattern in `expand()`. When `numReaders > 1`, this forces the 
distribution of reading tasks across available Beam workers.
   - **DoFn Refactoring**: Updated `ReadFromSparkReceiverWithOffsetDoFn` to 
accept explicit `Integer` shard identifiers instead of generic `byte[]`.
   - **Backward Compatibility**: Preserved strict backward compatibility. If 
`numReaders` is partially set or defaults to 1, the IO mimics the original 
behavior exactly.
   
   ## Issue Links
   Fixes #37410
   
   ## Type of change
   - [x] New feature
   
   ## Tests
   I have added a new unit test `testReadFromCustomReceiverWithParallelism` to 
`SparkReceiverIOTest.java` which verifies that:
   1. The IO correctly initializes with multiple readers (configured to 3).
   2. All records are read without duplication or loss (verified 60 total 
records from 3 simulated sources).
   
   Running the tests:
   ```bash
   ./gradlew :sdks:java:io:sparkreceiver:3:test
   
   ------------------------
   
   Thank you for your contribution! Follow this checklist to help us 
incorporate your contribution quickly and easily:
   
    - [ ] 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.
    - [ ] 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)
   
------------------------------------------------------------------------------------------------
   [![Build python source distribution and 
wheels](https://github.com/apache/beam/actions/workflows/build_wheels.yml/badge.svg?event=schedule&&?branch=master)](https://github.com/apache/beam/actions?query=workflow%3A%22Build+python+source+distribution+and+wheels%22+branch%3Amaster+event%3Aschedule)
   [![Python 
tests](https://github.com/apache/beam/actions/workflows/python_tests.yml/badge.svg?event=schedule&&?branch=master)](https://github.com/apache/beam/actions?query=workflow%3A%22Python+Tests%22+branch%3Amaster+event%3Aschedule)
   [![Java 
tests](https://github.com/apache/beam/actions/workflows/java_tests.yml/badge.svg?event=schedule&&?branch=master)](https://github.com/apache/beam/actions?query=workflow%3A%22Java+Tests%22+branch%3Amaster+event%3Aschedule)
   [![Go 
tests](https://github.com/apache/beam/actions/workflows/go_tests.yml/badge.svg?event=schedule&&?branch=master)](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]

Reply via email to