Change global var hash datatype to string #175
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
tkirschke
approved these changes
May 13, 2024
|
I also updated the wiki page for synapse accordingly. @tkirschke @tkiehn |
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 changes the global variable, as defined in the dbt_project.yml, for the
hash_datatypeback to String.For the case, that no global variable is defined in the dbt_project.yml the default-values for synapse were changed to Binary(16) (staging/synapse/stage.sql, supporting/hash.sql, tables/synapse/pit.sql).
To inform Synapse users of the correct value for the global variable an addition to the synapse specific notes should be made.