Remove unused columns from CR BigQuery queries#3687
Conversation
Remove columns selected but never consumed downstream in the component readiness test details query (both BigQuery and PostgreSQL providers): - test_suite: not parsed in deserializeRowToJobRunTestReportStatus - file_path: not parsed (kept in GROUP BY for correct aggregation) - capabilities: not parsed, saves reading from latest_component_mapping Also clean up stale TODOs and debug comments referencing jira_component and jira_component_id in the component report query, where those columns were never actually selected. Closes: https://issues.redhat.com/browse/TRT-2746 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
Pipeline controller notification For optional jobs, comment This repository is configured in: automatic mode |
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: mstaeble The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (2)
💤 Files with no reviewable changes (1)
WalkthroughThe PR removes unused test-detail columns from the BigQuery and PostgreSQL component-readiness queries and updates the related row-shape comments and struct fields to match the remaining selected data. ChangesComponent readiness query shape cleanup
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Suggested labels
Suggested reviewers
🚥 Pre-merge checks | ✅ 21✅ Passed checks (21 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Scheduling required tests: |
|
@mstaeble: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Summary
test_suite,file_path,capabilities) that are selected but never consumed in deserializationcapabilitiesfrom the PostgreSQL test details query for parityjira_component/jira_component_idin the component report query (they were never in the SELECT clause)Reduces bytes scanned per CR query, directly lowering BigQuery cost. The
capabilitiesremoval is the most impactful since it eliminates reading that column from thelatest_component_mappingtable.file_pathis kept in the GROUP BY to preserve correct aggregation semantics.Closes: https://issues.redhat.com/browse/TRT-2746
Test plan
gofmtcleango vet ./pkg/api/componentreadiness/...passesgo test ./pkg/api/componentreadiness/...passesmake testpassesgolangci-lint run ./...reports 0 issues🤖 Generated with Claude Code
Summary by CodeRabbit