Repository navigation
managed row-copy - #91
Open
shlomi-noach wants to merge 2 commits into
Open
shlomi-noach wants to merge 2 commits into
shlomi-noach wants to merge 2 commits into
Conversation
|
As an extension to this, it could be interesting to support filtering the table by some arbitrary query; this would essentially support sharding a table onto a new replica set (assuming hook functionality to change the write host externally rather than doing the table flip). It may well be outside the scope of the tool though. |
|
@DamianZaremba, I would say adding a |
Closed
This branch has not been deployed
This file contains hidden or 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
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.
WIP
phase 2: copy row data via app (configurable)
This will be an alternative to the
insert into...selectthat executes on the master. Instead, we can read row data from the replica, into the app, then write it back to the master.This further decouples the write load from master's load, or in fact decouples the entire migration from the master. The master just so happens to be the one where we apply the new table on.