Skip to content

Conversation

@tchow-zlai
Copy link
Collaborator

@tchow-zlai tchow-zlai commented Dec 20, 2024

Summary

Checklist

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

Summary by CodeRabbit

  • New Features

    • Introduced support for reading and writing data formats in Google Cloud Platform's BigQuery.
    • Added functionality for handling Google Cloud Storage (GCS) data in a Spark environment.
    • New method to check if a table is partitioned.
  • Bug Fixes

    • Enhanced error handling for missing project IDs and database names.
  • Tests

    • Expanded test coverage for BigQuery integration with new test cases.
  • Chores

    • Updated dependency management for improved clarity and compatibility.

## Summary

- Removing deprecated method
- A couple partition methods are used only in unit tests, going to move
them out of the main `TableUtils` so that we don't have to generally
support them.


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

- **New Features**
- Introduced a new utility class, `TableTestUtils`, for enhanced
partition management in Spark SQL.
- Added methods for dropping partitions and partition ranges in the new
utility class.

- **Bug Fixes**
- Improved error handling for partition insertion and schema validation
in tests.

- **Refactor**
	- Removed deprecated methods related to partition management.
- Updated test classes to utilize the new `TableTestUtils` for clarity
and specificity.

- **Style**
- Enhanced readability and formatting in test cases and schema
declarations.
<!-- 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":"tchow/bq-support-4","parentHead":"abd251cdadcea8c01fe11b8025358a275cc3eb38","parentPull":148,"trunk":"main"}
```
-->
@tchow-zlai tchow-zlai closed this Dec 20, 2024
@tchow-zlai tchow-zlai deleted the revert-153-tchow/remove-deprecated-code branch December 20, 2024 23:14
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Dec 20, 2024

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request introduces comprehensive changes to the Chronon project's Google Cloud Platform (GCP) integration, focusing on dependency management, BigQuery and Google Cloud Storage (GCS) format providers, and test infrastructure. The modifications enhance the project's ability to interact with cloud storage and data services by adding new classes, updating build configurations, and implementing robust testing mechanisms for cloud-based data operations.

Changes

File Change Summary
build.sbt Updated GCP project dependencies, added GCS connectors, specified Jackson dependency overrides
cloud_gcp/.../BigQueryFormat.scala New class implementing BigQuery format provider with read/write methods
cloud_gcp/.../GCSFormat.scala New class for Google Cloud Storage format handling
cloud_gcp/.../test/BigQueryCatalogTest.scala Added comprehensive test suite for BigQuery integration
spark/.../TableUtils.scala Updated method signatures, added isPartitioned method, annotated methods needing provider

Sequence Diagram

sequenceDiagram
    participant User
    participant GCPFormatProvider
    participant BQuery
    participant GCS
    participant SparkSession

    User->>GCPFormatProvider: readFormat(tableName)
    GCPFormatProvider->>SparkSession: Get table metadata
    alt BigQuery Provider
        GCPFormatProvider->>BQuery: Create BQuery instance
    else GCS Provider
        GCPFormatProvider->>GCS: Create GCS instance
    else Default
        GCPFormatProvider->>SparkSession: Return Hive format
    end
Loading

Possibly related PRs

Suggested Reviewers

  • piyush-zlai
  • nikhil-zlai

Poem

🌥️ In clouds of data, we dance and play,
Sparks of code light up our way
BigQuery whispers, GCS gleams bright
Dependencies aligned just right!
Cloud integration takes its flight 🚀


📜 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 ecfafbf and 7d4f313.

📒 Files selected for processing (5)
  • build.sbt (1 hunks)
  • cloud_gcp/src/main/scala/ai/chronon/integrations/cloud_gcp/BigQueryFormat.scala (1 hunks)
  • cloud_gcp/src/main/scala/ai/chronon/integrations/cloud_gcp/GCSFormat.scala (1 hunks)
  • cloud_gcp/src/test/scala/ai/chronon/integrations/cloud_gcp/test/BigQueryCatalogTest.scala (1 hunks)
  • spark/src/main/scala/ai/chronon/spark/TableUtils.scala (11 hunks)

🪧 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 docstrings to generate docstrings for this PR. (Beta)
  • @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.

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.

2 participants