Repository navigation
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| with: | ||
| persist-credentials: false | ||
| - name: Setup repository | ||
| uses: ./.github/actions/setup-action |
| - name: Setup repository | ||
| uses: ./.github/actions/setup-action | ||
| - name: Setup environment | ||
| uses: ./.github/actions/setup-environment-action |
| - name: Setup environment | ||
| uses: ./.github/actions/setup-environment-action | ||
| - name: run PostCommit Java Dataflow V2 scale tests | ||
| uses: ./.github/actions/gradle-command-self-hosted-action |
bvolpato
force-pushed
the
bvolpato/separate-bigquery-scale-validation
branch
from
October 28, 2026 05:16
f3c78f3 to
e4a4e60
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The 1 TB BigQuery read takes about 2h22 in the Dataflow V2 integration reports (example). It currently runs as part of the suite scheduled every eight hours.
Run that case unchanged in a dedicated daily V2 scale job. Keep the other BigQuery read cases in the regular suite and retain the existing explicit CI triggers for running both lanes. The tradeoff is daily rather than eight-hour feedback for the 1 TB case.
Validated the actual Gradle task graph and test selection with
--test-dry-run, plus workflow syntax. The two tasks retain the same V2 options, SDK build dependencies, classpath, and cleanup. The test input and row-count assertion are unchanged. No Dataflow jobs or SDK images were published during local validation.