chore: Remove some prints

[tchow-zlai]

Summary

Checklist

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

Summary by CodeRabbit

• Style

  • Reorganized import statements for improved readability.

• Chores

  • Removed debugging print statements from partition insertion to clean up console output.

[coderabbitai]

Walkthrough

This update reorganizes import statements in Extensions.scala for clarity and removes two debugging print statements from the insertPartitions method in TableUtils.scala. No logic, control flow, or public API changes are introduced.

Changes

File(s)	Change Summary
spark/src/main/scala/ai/chronon/spark/Extensions.scala	Reordered and grouped import statements for improved clarity.
spark/src/main/scala/ai/chronon/spark/catalog/TableUtils.scala	Removed two debugging print statements from the insertPartitions method.

Possibly related PRs

• refactor tableutils into its own module catalog #679: Refactors TableUtils by moving it into its own catalog module and updates import paths, relating to import organization and TableUtils changes.

Suggested reviewers

• nikhil-zlai
• varant-zlai

Poem

Imports aligned, the code now neat,
Debug prints gone, no more repeat!
Clarity reigns in every line,
TableUtils and Extensions shine.
With tidy code, we march ahead—
Onward, Chronon, boldly led!
✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6edb34b and 0573381.

📒 Files selected for processing (2)

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

💤 Files with no reviewable changes (1)

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

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

• GitHub Check: spark_tests
• GitHub Check: streaming_tests
• GitHub Check: streaming_tests
• GitHub Check: groupby_tests
• GitHub Check: fetcher_tests
• GitHub Check: analyzer_tests
• GitHub Check: analyzer_tests
• GitHub Check: groupby_tests
• GitHub Check: spark_tests
• GitHub Check: join_tests
• GitHub Check: join_tests
• GitHub Check: fetcher_tests
• GitHub Check: batch_tests
• GitHub Check: scala_compile_fmt_fix
• GitHub Check: batch_tests
• GitHub Check: enforce_triggered_workflows

🔇 Additional comments (1)

spark/src/main/scala/ai/chronon/spark/Extensions.scala (1)

19-24: Import cleanup approved. Consolidated and separated imports improve clarity.

---

🪧 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 docstrings to generate docstrings for this 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.