Skip to content

Conversation

@david-zlai
Copy link
Contributor

@david-zlai david-zlai commented May 14, 2025

Summary

^^^

Currently, we'll face unexpected behavior if multiple people are working and iterating on the same GroupBy/Join and changing the conf because we'll upload to the same GCS path.

This change adds the job id to the destination GCS path.

Checklist

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

Summary by CodeRabbit

  • Refactor
    • Streamlined job submission to upload a single metadata configuration file, simplifying the process.
    • Enhanced job ID management by requiring and propagating a job ID argument, improving job tracking and consistency.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented May 14, 2025

Walkthrough

The GcpRunner class was enhanced with a job_id attribute and its generate_dataproc_submitter_args method was changed to accept a single metadata config file path instead of multiple files. The method uploads this file to a GCS path including the job_id and appends the job ID argument. Corresponding Scala code was updated to require and reuse this job ID argument.

Changes

File(s) Change Summary
api/python/ai/chronon/repo/gcp.py Added job_id attribute; changed generate_dataproc_submitter_args to accept single metadata_conf_path; upload logic updated to use job_id in GCS path; all related calls adjusted accordingly.
cloud_gcp/src/main/scala/ai/chronon/integrations/cloud_gcp/DataprocSubmitter.scala Modified createSubmissionPropsMap to require jobId argument from input args, throwing if missing; removed unconditional UUID generation.
spark/src/main/scala/ai/chronon/spark/submission/JobSubmitter.scala Added JobIdArgKeyword = "--job-id" constant and included it in SharedInternalArgs.
cloud_gcp/src/test/scala/ai/chronon/integrations/cloud_gcp/DataprocSubmitterTest.scala Updated tests to include --job-id argument in calls to createSubmissionPropsMap and job submission methods for both Spark and Flink scenarios.

Possibly related PRs

Suggested reviewers

  • tchow-zlai

Poem

A single path, no longer a list,
Metadata uploads now can't be missed.
Arguments trimmed, the code is neat,
One config file, a tidy feat.
Simpler flows, less to debug—
Refactor done, give change a hug!

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.


Note

⚡️ Faster reviews with caching

CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.
Enjoy the performance boost—your workflow just got faster.


📜 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 9e6ee7e and e469f69.

📒 Files selected for processing (1)
  • cloud_gcp/src/test/scala/ai/chronon/integrations/cloud_gcp/DataprocSubmitterTest.scala (7 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (29)
  • GitHub Check: service_commons_tests
  • GitHub Check: cloud_gcp_tests
  • GitHub Check: streaming_tests
  • GitHub Check: service_tests
  • GitHub Check: streaming_tests
  • GitHub Check: cloud_aws_tests
  • GitHub Check: analyzer_tests
  • GitHub Check: online_tests
  • GitHub Check: join_tests
  • GitHub Check: service_tests
  • GitHub Check: spark_tests
  • GitHub Check: flink_tests
  • GitHub Check: groupby_tests
  • GitHub Check: groupby_tests
  • GitHub Check: cloud_gcp_tests
  • GitHub Check: analyzer_tests
  • GitHub Check: flink_tests
  • GitHub Check: join_tests
  • GitHub Check: cloud_aws_tests
  • GitHub Check: spark_tests
  • GitHub Check: api_tests
  • GitHub Check: fetcher_tests
  • GitHub Check: api_tests
  • GitHub Check: aggregator_tests
  • GitHub Check: scala_compile_fmt_fix
  • GitHub Check: batch_tests
  • GitHub Check: aggregator_tests
  • GitHub Check: python_tests
  • GitHub Check: batch_tests
🔇 Additional comments (7)
cloud_gcp/src/test/scala/ai/chronon/integrations/cloud_gcp/DataprocSubmitterTest.scala (7)

116-117: Added required job-id argument for spark job tests.

This change correctly adds the necessary job-id parameter to the test case, properly validating the new job ID requirement.


164-165: Added job-id to Flink job with latest savepoint test.

Consistent with the PR objective of ensuring unique metadata paths by including job ID.


206-207: Added job-id to Flink job with no savepoint test.

Properly implements the job ID parameter requirement.


251-252: Added job-id to Flink job with user savepoint test.

Consistent implementation of job ID parameter.


480-481: Added job-id to Flink no-savepoint deploy strategy test.

Correctly implements job ID for the deployment test case.


534-535: Added job-id to Flink latest savepoint deploy test.

Aligns with other changes to include job ID in all test cases.


597-598: Added job-id to Flink user savepoint deploy test.

Completes the implementation of job ID parameters across all test cases.


🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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 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.

@david-zlai david-zlai requested a review from tchow-zlai May 14, 2025 21:37

val jobId = UUID.randomUUID().toString
val jobId = JobSubmitter
.getArgValue(args, JobIdArgKeyword)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

probably just make this required then, and fail if it's not passed.

@david-zlai david-zlai merged commit 30f5356 into main May 15, 2025
35 checks passed
@david-zlai david-zlai deleted the davidhan/upload_to_different_metadata branch May 15, 2025 00:59
chewy-zlai pushed a commit that referenced this pull request May 15, 2025
…ons (#771)

## Summary

^^^

Currently, we'll face unexpected behavior if multiple people are working
and iterating on the same GroupBy/Join and changing the conf because
we'll upload to the same GCS path.

This change adds the job id to the destination GCS path.

## Checklist
- [ ] Added Unit Tests
- [ ] Covered by existing CI
- [x] Integration tested
- [ ] Documentation update



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **Refactor**
- Streamlined job submission to upload a single metadata configuration
file, simplifying the process.
- Enhanced job ID management by requiring and propagating a job ID
argument, improving job tracking and consistency.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
chewy-zlai pushed a commit that referenced this pull request May 15, 2025
…ons (#771)

## Summary

^^^

Currently, we'll face unexpected behavior if multiple people are working
and iterating on the same GroupBy/Join and changing the conf because
we'll upload to the same GCS path.

This change adds the job id to the destination GCS path.

## Checklist
- [ ] Added Unit Tests
- [ ] Covered by existing CI
- [x] Integration tested
- [ ] Documentation update



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **Refactor**
- Streamlined job submission to upload a single metadata configuration
file, simplifying the process.
- Enhanced job ID management by requiring and propagating a job ID
argument, improving job tracking and consistency.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
chewy-zlai pushed a commit that referenced this pull request May 16, 2025
…ons (#771)

## Summary

^^^

Currently, we'll face unexpected behavior if multiple people are working
and iterating on the same GroupBy/Join and changing the conf because
we'll upload to the same GCS path.

This change adds the job id to the destination GCS path.

## Cheour clientslist
- [ ] Added Unit Tests
- [ ] Covered by existing CI
- [x] Integration tested
- [ ] Documentation update



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **Refactor**
- Streamlined job submission to upload a single metadata configuration
file, simplifying the process.
- Enhanced job ID management by requiring and propagating a job ID
argument, improving job traour clientsing and consistency.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
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.

3 participants