Skip to content

chore: drop tables in the join integration test #735

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 5, 2025

Conversation

tchow-zlai
Copy link
Collaborator

@tchow-zlai tchow-zlai commented May 5, 2025

Summary

  • Drop tables in the join integration tests.

Checklist

  • Added Unit Tests
  • Covered by existing CI
  • Integration tested
  • Documentation update

Summary by CodeRabbit

  • Chores
    • Enhanced cleanup process to remove additional BigQuery tables in "canary" and "dev" environments.

Copy link

coderabbitai bot commented May 5, 2025

Walkthrough

The cleanup phase of the run_gcp_quickstart.sh script has been updated to delete an additional BigQuery table for both the "canary" and "dev" environments. Specifically, it now removes data.gcp_training_set_v1_test in "canary" and data.gcp_training_set_v1_dev in "dev", in addition to the previously targeted tables. No other logic or control flow changes are present.

Changes

File(s) Change Summary
scripts/distribution/run_gcp_quickstart.sh Enhanced cleanup: now deletes extra BigQuery tables (v1_test for "canary", v1_dev for "dev")

Suggested reviewers

  • david-zlai

Poem

When cleaning up, let none remain,
Extra tables swept from the domain.
"Dev" and "canary" both wiped clean,
In scripts where tidy code is seen.
Bash commands march, delete, and run—
The quickstart's work is never done!
🧹✨

Warning

Review ran into problems

🔥 Problems

GitHub Actions and Pipeline Checks: Resource not accessible by integration - https://docs.github.com/rest/actions/workflow-runs#list-workflow-runs-for-a-repository.

Please grant the required permissions to the CodeRabbit GitHub App under the organization or repository settings.


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro (Legacy)

📥 Commits

Reviewing files that changed from the base of the PR and between 6be5dec and 514525d.

📒 Files selected for processing (1)
  • scripts/distribution/run_gcp_quickstart.sh (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • scripts/distribution/run_gcp_quickstart.sh

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@tchow-zlai tchow-zlai changed the title join chore: drop tables in the join integration test May 5, 2025
@tchow-zlai tchow-zlai requested a review from david-zlai May 5, 2025 19:00
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro (Legacy)

📥 Commits

Reviewing files that changed from the base of the PR and between c16b583 and 6be5dec.

📒 Files selected for processing (1)
  • scripts/distribution/run_gcp_quickstart.sh (1 hunks)
🔇 Additional comments (1)
scripts/distribution/run_gcp_quickstart.sh (1)

74-74: Verify BigQuery table name syntax
Confirm that data.gcp_training_set.v1_test is a valid table identifier. BigQuery table IDs typically can’t contain dots—this may need to be gcp_training_set_v1_test or use data.gcp_training_set as the dataset and v1_test as the table.

else
bq rm -f -t canary-443022:data.gcp_purchases_v1_dev
bq rm -f -t canary-443022:data.gcp_purchases_v1_view_dev
bq rm -f -t canary-443022:data.gcp_purchases_v1_dev_upload
bq rm -f -t canary-443022:data.gcp_training_set.v1_dev
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Parameterize project ID for both environments
You’re hard-coding canary-443022 even in the dev branch, which risks deleting the wrong tables. Introduce a PROJECT_ID (e.g. based on $ENVIRONMENT) and reference it here to DRY up and safeguard these calls.

@tchow-zlai tchow-zlai merged commit 742958d into main May 5, 2025
4 checks passed
@tchow-zlai tchow-zlai deleted the tchow/drop-integ-join-tables branch May 5, 2025 19:09
chewy-zlai pushed a commit that referenced this pull request May 15, 2025
## Summary

- Drop tables in the join integration tests. 

## Checklist
- [ ] Added Unit Tests
- [ ] Covered by existing CI
- [ ] Integration tested
- [ ] Documentation update
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **Chores**
- Enhanced cleanup process to remove additional BigQuery tables in
"canary" and "dev" environments.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

<!-- av pr metadata
This information is embedded by the av CLI when creating PRs to track
the status of stacks when using Aviator. Please do not delete or edit
this section of the PR.
```
{"parent":"main","parentHead":"","trunk":"main"}
```
-->

---------

Co-authored-by: thomaschow <[email protected]>
chewy-zlai pushed a commit that referenced this pull request May 15, 2025
## Summary

- Drop tables in the join integration tests. 

## Checklist
- [ ] Added Unit Tests
- [ ] Covered by existing CI
- [ ] Integration tested
- [ ] Documentation update
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **Chores**
- Enhanced cleanup process to remove additional BigQuery tables in
"canary" and "dev" environments.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

<!-- av pr metadata
This information is embedded by the av CLI when creating PRs to track
the status of stacks when using Aviator. Please do not delete or edit
this section of the PR.
```
{"parent":"main","parentHead":"","trunk":"main"}
```
-->

---------

Co-authored-by: thomaschow <[email protected]>
chewy-zlai pushed a commit that referenced this pull request May 16, 2025
## Summary

- Drop tables in the join integration tests. 

## Cheour clientslist
- [ ] Added Unit Tests
- [ ] Covered by existing CI
- [ ] Integration tested
- [ ] Documentation update
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **Chores**
- Enhanced cleanup process to remove additional BigQuery tables in
"canary" and "dev" environments.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

<!-- av pr metadata
This information is embedded by the av CLI when creating PRs to traour clients
the status of staour clientss when using Aviator. Please do not delete or edit
this section of the PR.
```
{"parent":"main","parentHead":"","trunk":"main"}
```
-->

---------

Co-authored-by: thomaschow <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants