feat: BigQuery views

[tchow-zlai]

Summary

Checklist

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

Summary by CodeRabbit

• New Features
  • Added support for handling BigQuery views when loading tables, improving compatibility with a wider range of BigQuery table types.
• Bug Fixes
  • Updated internal handling of partition column aliases to ensure accurate retrieval of partition data from BigQuery tables.

[coderabbitai]

Walkthrough

The update enhances the loadTable method in DelegatingBigQueryMetastoreCatalog by introducing support for BigQuery views. The method now checks if a table definition is a ViewDefinition and, if so, delegates the loading to connectorCatalog using a constructed identifier. Additionally, a constant alias for the distinct partition column in BigQuery SQL queries was renamed for clarity. The rest of the method's logic and error handling remain unchanged, and there are no changes to public APIs.

Changes

File(s)	Change Summary
cloud_gcp/src/main/scala/ai/chronon/integrations/cloud_gcp/DelegatingBigQueryMetastoreCatalog.scala	Added handling for BigQuery views in loadTable, delegating view loading to connectorCatalog.
cloud_gcp/src/main/scala/ai/chronon/integrations/cloud_gcp/BigQueryNative.scala	Renamed internal alias for distinct partition column from __chronon_internal_bq_col__ to __chronon_internal_bq_partition_col__ in SQL and DataFrame code.

Possibly related PRs

• feat: Make delegating BigQueryMetastore just a SparkCatalog #520: Restructures DelegatingBigQueryMetastoreCatalog and modifies loadTable error handling, related to view handling changes.
• chore: Remove use of DelegatingTable and bubble up exceptions properly #638: Simplifies loadTable by removing wrappers, overlaps with table loading logic.
• fix: address bug in loadTable handling namespaces #637: Changes method signature and identifier handling in loadTable, related to view support.

Poem

🚀 In clouds where data flows,
Views now join the show.
Delegation’s clever art,
Loads views right from the start.
Catalogs link, queries gleam—
BigQuery’s new dream team! 🌟

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 4f181cb and a23d8fe.

📒 Files selected for processing (1)

• cloud_gcp/src/main/scala/ai/chronon/integrations/cloud_gcp/BigQueryNative.scala (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• cloud_gcp/src/main/scala/ai/chronon/integrations/cloud_gcp/BigQueryNative.scala

⏰ Context from checks skipped due to timeout of 90000ms (19)

• GitHub Check: service_tests
• GitHub Check: service_tests
• GitHub Check: cloud_gcp_tests
• GitHub Check: service_commons_tests
• GitHub Check: cloud_aws_tests
• GitHub Check: cloud_gcp_tests
• GitHub Check: hub_tests
• GitHub Check: cloud_aws_tests
• GitHub Check: online_tests
• GitHub Check: hub_tests
• GitHub Check: api_tests
• GitHub Check: aggregator_tests
• GitHub Check: flink_tests
• GitHub Check: flink_tests
• GitHub Check: aggregator_tests
• GitHub Check: api_tests
• GitHub Check: scala_compile_fmt_fix
• GitHub Check: online_tests
• GitHub Check: enforce_triggered_workflows

---

🪧 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.

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.