Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(store/v2): cleanup the migration API #20298

Merged
merged 5 commits into from May 13, 2024
Merged

chore(store/v2): cleanup the migration API #20298

merged 5 commits into from May 13, 2024

Conversation

cool-develope
Copy link
Contributor

@cool-develope cool-develope commented May 6, 2024

Description

Closes: #20203


Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

  • included the correct type prefix in the PR title
  • confirmed ! in the type prefix if API or client breaking change
  • targeted the correct branch (see PR Targeting)
  • provided a link to the relevant issue or specification
  • reviewed "Files changed" and left comments if necessary
  • included the necessary unit and integration tests
  • added a changelog entry to CHANGELOG.md
  • updated the relevant documentation or specification, including comments for documenting Go code
  • confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

  • confirmed the correct type prefix in the PR title
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

Summary by CodeRabbit

  • New Features

    • Introduced a new function to create instances of Store with an optional migration manager.
    • Enhanced the Query and Commit methods in Store to handle operations based on migration status.
  • Refactor

    • Updated the migration process to be handled asynchronously within the Store.
  • Bug Fixes

    • Added a pre-migration check to ensure fallback to the original state before migration.
  • Tests

    • Simplified the test suite by removing tests for non-existent key querying and fallback behavior.
  • Chores

    • Removed the StartMigration function from the RootStore interface as it's no longer needed.

@cool-develope cool-develope requested a review from a team as a code owner May 6, 2024 16:34
Copy link
Contributor

coderabbitai bot commented May 6, 2024

Walkthrough

Walkthrough

The changes encompass enhancing the Store structure in store.go by introducing a new function for instance creation, refactoring the Query and Commit methods to handle migration status, and updating migration handling. Additionally, outdated functions and tests related to fallback and migration triggers are removed to streamline testing and interface definitions.

Changes

Files Change Summary
store/v2/root/migrate_test.go Included a check for Query fallback before starting migration.
store/v2/root/store.go Added New function, refactored Query and Commit, and updated migration handling.
store/v2/root/store_test.go Eliminated TestGetFallback function.
store/v2/store.go Removed StartMigration from RootStore interface.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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.

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 as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

Copy link
Contributor

github-actions bot commented May 6, 2024

@cool-develope your pull request is missing a changelog!

@cool-develope cool-develope changed the title cleanup the migration API chore(store/v2): cleanup the migration API May 6, 2024
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

Review Details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits Files that changed from the base of the PR and between 271a46c and 16f9fa8.
Files selected for processing (4)
  • store/v2/root/migrate_test.go (1 hunks)
  • store/v2/root/store.go (7 hunks)
  • store/v2/root/store_test.go (1 hunks)
  • store/v2/store.go (1 hunks)
Files skipped from review due to trivial changes (1)
  • store/v2/root/store_test.go
Additional Context Used
Path-based Instructions (3)
store/v2/store.go (1)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.

store/v2/root/migrate_test.go (2)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.


Pattern **/*_test.go: "Assess the unit test code assessing sufficient code coverage for the changes associated in the pull request"

store/v2/root/store.go (1)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.

Additional comments not posted (6)
store/v2/store.go (1)

Line range hint 1-1: Removal of StartMigration() from RootStore interface aligns with PR objectives.

store/v2/root/migrate_test.go (1)

90-99: Ensure the new test for query fallback to the original SC is comprehensive and correctly implemented.

store/v2/root/store.go (4)

Line range hint 62-79: The new New constructor correctly initializes the Store with a migration manager if provided.


170-177: Modification to the Query method to handle queries based on migration status is correctly implemented.


295-306: Ensure that the conditional logic in the Commit method correctly handles state storage commits when not migrating.


348-352: The startMigration method is correctly implemented to handle asynchronous migration operations.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

Review Details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits Files that changed from the base of the PR and between 16f9fa8 and 8d10895.
Files selected for processing (2)
  • store/v2/migration/manager.go (1 hunks)
  • store/v2/root/store.go (7 hunks)
Files skipped from review as they are similar to previous changes (1)
  • store/v2/root/store.go
Additional Context Used
Path-based Instructions (1)
store/v2/migration/manager.go (1)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.

store/v2/migration/manager.go Show resolved Hide resolved
@tac0turtle tac0turtle added this pull request to the merge queue May 13, 2024
Merged via the queue into main with commit 559f784 May 13, 2024
67 of 68 checks passed
@tac0turtle tac0turtle deleted the store/mig_clean branch May 13, 2024 12:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Avoid to write & query against SS while migration
3 participants