Add Scripts to Import/ Export Datasets #11
Merged
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
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.
Milestone towards finishing out #6
elasticsearch/export_index.sh and elasticsearch/import_index.sh have been added. These scripts allow you to move an elasticsearch dataset between instances of elasticsearch. We can build upon these scripts to load in sample data at install time.
One unfortunate thing about this PR is that it does expose the elasticsearch credentials in the output. From what I can tell, there is no way to avoid this while using elasticdump short of sending all of the output to
/dev/null. I didn't send the output to the garbage bin for now since I figure it would be helpful for any debugging that we may run into in the near future.