segregated indexer: handler trait and migrate snapshot_objects table #19623
+300
−151
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Skipped Deployments
|
gegaowp
commented
Sep 30, 2024
gegaowp
commented
Sep 30, 2024
| @@ -1,10 +1,10 @@ | |||
| // Copyright (c) Mysten Labs, Inc. | |||
| // SPDX-License-Identifier: Apache-2.0 | |||
| use std::sync::{Arc, Mutex}; | |||
There was a problem hiding this comment.
will rename the file to _handler before merging, leaving it for now for PR review.
bmwill
reviewed
Sep 30, 2024
gegaowp
changed the title
phoenix-o
approved these changes
Oct 2, 2024
lxfind
reviewed
Oct 2, 2024
lxfind
reviewed
Oct 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
main changes are:
handlertrait for each segregated indexer handler including impl. of common codesTest plan
added integration tests for objects_snapshot table
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.