Fix additional confs and update log uri for EMR

[david-zlai]

Summary

Checklist

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

Summary by CodeRabbit

• Bug Fixes
  • Updated job submission settings to ensure that additional configuration files are correctly referenced with the new dynamic path.
  • Adjusted AWS log storage so that EMR job logs are now directed to a dedicated logs bucket for improved consistency.

[coderabbitai]

Walkthrough

This diff modifies AWS-related configurations. In the Python module, the command string in AwsRunner.generate_emr_submitter_args now prepends a constant to the additional config file path to produce "/mnt/zipline/additional-confs.yaml". In the Scala module, the EMR log URI has been updated to reference a new S3 bucket naming convention from "zipline-artifacts" to "zipline-logs". No changes were made to public entity declarations.

Changes

File(s)	Change Summary
api/py/ai/chronon/repo/aws.py	Updated download_zipline_aws_jar and generate_emr_submitter_args methods: changed JAR path to release/latest/jars/{jar_name} and updated additional config path to "/mnt/zipline/additional-confs.yaml".
cloud_aws/src/main/scala/ai/chronon/integrations/aws/EmrSubmitter.scala	Changed log URI for EMR submissions from s"s3://zipline-artifacts-${customerId}/emr/" to s"s3://zipline-logs-${customerId}/emr/".
cloud_aws/src/test/scala/ai/chronon/integrations/aws/EmrSubmitterTest.scala	Updated expected log URI in EmrSubmitterTest from "s3://zipline-artifacts-canary/emr/" to "s3://zipline-logs-canary/emr/".

Suggested reviewers

• nikhil-zlai
• piyush-zlai
• chewy-zlai

Poem

In lines of code we weave a tale,
Paths aligned, adjustments never fail,
Mounts and logs in a fresh new light,
Revamped to run so smooth and right,
Cheers to code that takes flight!

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 e60c69a and b956698.

📒 Files selected for processing (2)

• api/py/ai/chronon/repo/aws.py (2 hunks)
• cloud_aws/src/test/scala/ai/chronon/integrations/aws/EmrSubmitterTest.scala (1 hunks)

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

• api/py/ai/chronon/repo/aws.py

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

• GitHub Check: non_spark_tests
• GitHub Check: scala_compile_fmt_fix
• GitHub Check: non_spark_tests
• GitHub Check: enforce_triggered_workflows

🔇 Additional comments (1)

cloud_aws/src/test/scala/ai/chronon/integrations/aws/EmrSubmitterTest.scala (1)

57-57: Change to log URI bucket.

Updated S3 path from "zipline-artifacts-canary" to "zipline-logs-canary".

---

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