[DAT-17952] Add support for ARRAY, MAP and Struct datatypes #181
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
filipelautert
changed the title
…omplex types as Liquibase core does not know how to handle values between <> in the data type.
KushnirykOleh
force-pushed
the
DAT-17952
branch
from
7da8f34 to
d44d6ce
Compare
KushnirykOleh
approved these changes
Sep 11, 2024
|
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.
Add support to allow snapshotting ARRAY, MAP and STRUCT datatypes .
Liquibase core does not know how to handle values between <> in the data type, so we would need to create infinite type options as you can have an array of struct with maps and arrays and etc.
To implement it we just ignore our datatypes and pass forward the type provided by Databricks.