Skip to content

managed row-copy - #91

Open
shlomi-noach wants to merge 2 commits into
masterfrom
row-copy-by-app
Open

shlomi-noach wants to merge 2 commits into
masterfrom
row-copy-by-app

Conversation

@shlomi-noach

Copy link
Copy Markdown
Contributor

WIP

phase 2: copy row data via app (configurable)

This will be an alternative to the insert into...select that 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.

@shlomi-noach shlomi-noach changed the title managed ro-copy managed row-copy Jul 8, 2016
@DamianZaremba

Copy link
Copy Markdown

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.

@tomkrouper

Copy link
Copy Markdown

@DamianZaremba, I would say adding a --where type option, like you are suggesting would be separate from this, and a good idea. Can you open an issue referencing this one with any details you'd like to see in such a feature?

This branch has not been deployed

No deployments
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