Feature/master thesis schema evolution in polystores #429
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
# Conflicts: # dbms/src/main/java/org/polypheny/db/processing/DataMigratorImpl.java # sql-language/src/main/codegen/config.fmpp # sql-language/src/main/java/org/polypheny/db/sql/language/ddl/altertable/SqlAlterTableMergeColumns.java
The MergeColumns feature
…lution-in-polystores' into feature/transfer-table-old-concept # Conflicts: # dbms/src/main/java/org/polypheny/db/processing/DataMigratorImpl.java # webui/src/main/java/org/polypheny/db/webui/Crud.java
The TransferTable feature
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.
Summary
MergeColumns: Allows merging multiple columns of a table in a relational namespace of Polypheny. As a test, the MergeColumns operation was performed in a vertically partitioned schema, where the one merging column in a document based store while the other is placed in a relational store.
TransferTable: This operation allows tables to be moved from one relational namespace to another relational or to a document-based namespace, and also allows a collection to be moved to either type of namespace. Here the challenge and the scope is also increasing. Moving a table or collection (depending on the type of schema) to another namespace of the same data model, through a simple but elegant solution, does not require migration, just changing the metadata of the Polypheny-DB’s catalog. The second approach, where a table from a relational namespace is about to be moved to a document-based namespace, requires both schema evolution and data migration, explains the differences in data storage depending on the global namespace, but is only shown for the simple case where the table being moved is not included related to other tables. The third approach, moving a collection to a relational namespace, also considers embedded/nested documents from which multiple tables related to each other are then created.
Changes
Features