This repository was archived by the owner on May 1, 2024. It is now read-only.
Spike: copy S3 database/schema data to another location in S3 #800
Conversation
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
brianhw
requested review from
HassanJaveed84,
bmedx,
doctoryes,
estute,
hunytalk,
macdiesel and
pwnage101
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Support copying Mysql database data on S3 from one location to another. Do the same for Vertica schema. Main purpose is to move S3 data to be used as a "reference" to a separate location in S3 from that used for daily production runs.
This is mostly for demonstration at this point, since it requires installing awscli on the cluster.