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

   ### What changed
   
   Fixes #38770
   
   This fixes handling of `num_storage_api_streams` / `num_streams` for 
BigQuery Storage Write API batch writes.
   
   Previously, the Java schema transform only applied `num_streams` inside the 
unbounded pipeline branch, so bounded batch pipelines using the Storage Write 
API ignored the configured fixed stream count. This change applies 
`withNumStorageWriteApiStreams(...)` whenever `num_streams > 0`, while keeping 
triggering frequency and auto-sharding behavior limited to unbounded pipelines.
   
   ### Details
   
   * Applies fixed Storage Write API stream counts to bounded and unbounded 
schema transform writes.
   * Keeps `auto_sharding` as an unbounded-only option.
   * Removes outdated documentation that described `num_storage_api_streams` / 
`num_streams` as streaming-only.
   * Updates Java, Python, and website docs to reflect batch support.
   * Adds a bounded pipeline translation test that verifies fixed stream counts 
produce the expected batch redistribute step.
   
   ### Validation
   
   * `git diff --check`
   * `./gradlew.bat --no-daemon --console=plain 
:sdks:java:io:google-cloud-platform:spotlessCheck`
   
   ### CHANGES.md
   
   Not updated because this is a targeted behavior/documentation fix rather 
than a broad user-facing feature addition.
   
   ---
   
   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.
   * [ ] 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)](https://www.apache.org/licenses/icla.pdf).
   
   See the [[Contributor 
Guide](https://beam.apache.org/contribute)](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)](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
   
   ## 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)](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)](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