Cli Command to migrate between databases #117
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
… another Is not yet fully implemented!
mixes up descriptorid and retrievableid when migrating file descriptors from json to postgres...
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.
This PR adds a new
migrate-toCli command to migrate all contents of one schema to another. For example to easily migrate from an existing cottontail database to postgres.Usage:
<origin-schema> migrate-to -n <target-schema>Both schemas need to be initialised
<schema> initand contain the same entities.Wiki: https://github.com/vitrivr/vitrivr-engine/wiki/Example#migration