Change log level to info for when no partitions found or unreachable table.

[david-zlai]

…table.

Summary

Checklist

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

Summary by CodeRabbit

• Logging
  • Adjusted log levels for table accessibility and partition availability messages from error to info.

[coderabbitai]

Walkthrough

The pull request modifies the logging behavior in the TableUtils.scala file, specifically changing log messages related to table accessibility and partition availability from error-level to info-level logs. This adjustment alters how the application reports issues with table reachability and partition discovery, reducing the perceived severity of these events.

Changes

File	Change Summary
spark/src/main/scala/ai/chronon/spark/TableUtils.scala	Modified log levels from ERROR to INFO for table reachability and partition discovery messages

Possibly related PRs

• feat: enable slf4j logging to work with logback #76: Introduces SLF4J logging with Logback
• chore: small cleanup of TableUtils #153: Previous changes to TableUtils class
• Allow info logs for ai.chronon.spark for dataproc. #194: Sets logging level for "ai.chronon.spark" logger to INFO

Suggested Reviewers

• nikhil-zlai
• piyush-zlai
• tchow-zlai

Poem

🌟 Logs that once screamed with might
Now whisper softly, info's light
From error's loud and jarring tone
To gentle notes, more calmly shown
A logging dance of subtle grace 🎭

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 e9f3dae and 04fda9e.

📒 Files selected for processing (1)

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

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

• GitHub Check: table_utils_delta_format_spark_tests
• GitHub Check: other_spark_tests
• GitHub Check: mutation_spark_tests
• GitHub Check: join_spark_tests
• GitHub Check: scala_compile_fmt_fix
• GitHub Check: fetcher_spark_tests
• GitHub Check: enforce_triggered_workflows

🔇 Additional comments (2)

spark/src/main/scala/ai/chronon/spark/TableUtils.scala (2)

188-188: LGTM! Log level change is appropriate.

Changed log level from error to info for unreachable table scenario.

---

197-197: LGTM! Log level change is appropriate.

Changed log level from error to info for no partitions found scenario.

---

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