feat: Set iceberg table options through table properties

[tchow-zlai]

Summary

• We want users to be able to specify write options. In the case of iceberg tables, these can be set at the table level through table properties. The chronon API already supports table properties, so let's just ride on those rails.
• Users can set write distribution options through this mechanism: https://iceberg.apache.org/docs/latest/spark-writes/#writing-distribution-modes

Checklist

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

Summary by CodeRabbit

• New Features
  • Enabled dynamic updates of table properties during partition insertions, offering more flexible table management.
• Refactor
  • Streamlined table write operations by removing legacy configuration options to simplify data handling.

[coderabbitai]

Walkthrough

This PR updates the insertPartitions method in TableUtils by conditioning the alteration of table properties. When valid table properties are provided, it triggers a SQL command via alterTablePropertiesSql to update the table. Additionally, two fixed write options (distribution mode and target file size) have been removed, simplifying the data write configuration.

Changes

File	Change Summary
spark/.../TableUtils.scala	Added conditional SQL execution for altering table properties in insertPartitions; removed fixed .option("distribution-mode", "none") and file size options

Sequence Diagram(s)

sequenceDiagram
    participant C as Caller
    participant T as TableUtils
    participant S as SQL Engine

    C->>T: Call insertPartitions(data, tableProperties)
    T->>T: Check if tableProperties are provided
    alt tableProperties valid
        T->>S: Execute ALTER SQL via alterTablePropertiesSql
    else 
        Note right of T: Skip altering properties
    end
    T->>C: Continue partition insertion

Loading

Possibly related PRs

• feat: use direct writes to bigquery #264: Related changes to insertPartitions handling table properties and data writing.
• feat: refactor for alter tables #272: Enhancements for altering table properties during partition insertion.
• chore: refactor creationUtils to not use formatProvider #260: Modifications to insertPartitions for file format specifications.

Suggested reviewers

• piyush-zlai
• nikhil-zlai
• varant-zlai

Poem

In TableUtils the code does sing,
With properties dynamic, it takes wing.
SQL alters the table with a bright new cue,
Two options fade, making space for the new.
Cheers to progress in every line we bring!
🚀✨

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 686803d and 00ec26b.

📒 Files selected for processing (1)

• spark/src/main/scala/ai/chronon/spark/TableUtils.scala (1 hunks)

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

• spark/src/main/scala/ai/chronon/spark/TableUtils.scala

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

• GitHub Check: scala_compile_fmt_fix
• GitHub Check: streaming_tests
• GitHub Check: streaming_tests
• GitHub Check: analyzer_tests
• GitHub Check: spark_tests
• GitHub Check: spark_tests
• GitHub Check: groupby_tests
• GitHub Check: join_tests
• GitHub Check: join_tests
• GitHub Check: groupby_tests
• GitHub Check: analyzer_tests
• GitHub Check: fetcher_tests
• GitHub Check: fetcher_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 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.