Skip to content

[CI] Route BigQuery read tests by size - #40858

Draft
bvolpato wants to merge 1 commit into
apache:masterfrom
bvolpato:bvolpato/separate-bigquery-scale-validation
Draft

bvolpato wants to merge 1 commit into
apache:masterfrom
bvolpato:bvolpato/separate-bigquery-scale-validation

Conversation

@bvolpato

@bvolpato bvolpato commented Oct 28, 2026 •

Copy link
Copy Markdown
Contributor

The BigQuery read cases currently run only in the Dataflow V2 integration suite, including a 1 TB read that takes about 2h22 (example run). The smaller cases are excluded from GCP IO precommit and V1 has no coverage from this test class.

Run the empty and 1 MB cases in GCP IO Direct precommit, and the 1 GB case in both V1 and V2 integration. Move the unchanged 1 TB case to the existing BigQuery Batch Avro performance workflow on its twelve-hour schedule. Its existing test reads 10 GB, so keep the larger fixture and row-count assertion. Increase that workflow's timeout from 100 to 480 minutes to accommodate the additional workload.

Validated the actual Gradle task graph, pipeline options, CLI filter scoping and test discovery with --test-dry-run. The SDK image dependency and cleanup remain in place. Workflow syntax and actionlint passed. Live Dataflow execution and image builds were not run locally.

@github-actions github-actions Bot added build runners dataflow size/m M: 50-249 lines changed labels Oct 28, 2026
Comment thread .github/workflows/beam_PostCommit_Java_DataflowV2_Scale.yml Fixed
Comment thread .github/workflows/beam_PostCommit_Java_DataflowV2_Scale.yml Fixed
Comment thread .github/workflows/beam_PostCommit_Java_DataflowV2_Scale.yml Fixed
@bvolpato
bvolpato force-pushed the bvolpato/separate-bigquery-scale-validation branch from f3c78f3 to e4a4e60 Compare October 28, 2026 05:16
@Abacn

Abacn commented Oct 28, 2026

Copy link
Copy Markdown
Contributor

Thanks for bringing up this, this test exists for long and I agree the current config sounds odd

  • BigQueryIOReadIT is excluded from PreCommit, Dataflow Integration test v1 but executed on Integration test v2

I think what we should do is

  • Run testEmpty and test1M on PreCommit GCP IO
  • Run test1G on both integration test v1 and v2
  • Simply remove test 1T as if it's already covered by a beam_PerformanceTests. If not, run it in a beam_PerformanceTests test suite

@bvolpato
bvolpato force-pushed the bvolpato/separate-bigquery-scale-validation branch from e4a4e60 to d067e00 Compare October 29, 2026 00:01
@bvolpato bvolpato changed the title [CI] Run the 1 TB BigQuery read in a daily scale job [CI] Route BigQuery read tests by size Oct 29, 2026
@github-actions github-actions Bot added java io gcp size/s S: 10-49 lines changed and removed size/m M: 50-249 lines changed labels Oct 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants