Releases: ScalefreeCOM/datavault4dbt
v1.1.4
ATTENTION! IMPORTANT DISCLAIMER FOR v1.1.4
There is a fix for the hashing algorithm in the Snowflake adapter that will generate different hash for columns with strings containing the small character 'v' . The reason behind this is that Snowflake doesnt interpret the \v as a special character alias for the vertical tab, so instead it interprets that you are escaping the letter v
. The issue was first presented at #109
This fix means if you have a BK with value 'virtual'
, for example, in version 1.1.3 or earlier versions the hash algorithm was actually removing the small character 'v', so the value to be hashed was 'irtual'
(which is wrong), the value to be hashed should be 'virtual'
, in PR #118 we fix the hash so that it will now hash the correct value.
Therefore, if this key comes into the stage it will be hashed and generate a different hash value than the one encountered previously loaded in your Raw Vault. This hashkey will then be inserted into you Raw Vault, even though it represents the same BK, because it was not inserted before.
We strongly recommend that the user manually modifies the hashes which include this small character in the Raw Vault, updating the value to the correct one generated by the hash algorithm in this presented version, so that your stage wont falsely detect "new" keys.
We deeply apologize for the inconvenience that this generates.
Kind regards,
Your Scalefree datavault4dbt team.
What's Changed
All adapters - new feature and fix:
- Extended logarithmic logic of snapshot control tables by @bschlottfeldt in #116
- Fixed sat_v0 : Same hashdiff being inserted again into satellite without in between deltas by @bschlottfeldt in #123
Snowflake adapter - fix and new feature:
- Fixed replacement of vertical tab in hash_standardization - Snowflake adapter by @thoffmann-sf in #118
- Added RTRIM Hashdiff Option for Snowflake by @bschlottfeldt in #119 - More information on how to use this new feature can be found in https://github.com/ScalefreeCOM/datavault4dbt/wiki/Adding-new-columns-to-Hashdiff-and-Satellite
New Contributors
- @thoffmann-sf made their first contribution in #118
Full Changelog: v1.1.3...v1.1.4
Hotfix v1.1.3
What's Changed
- Fix typo in README.md by @sergeyh in #106
- Changed minor Syntax-Error for Satellite v1 Macros by @JPLangner in #111
- Use count(*) for incremental logic in rec_track_sat by @tkirschke in #114
- Applied fix in rec_track_sat macro for Exasol and BigQuery by @bschlottfeldt in #115
New Contributors
Full Changelog: v1.1.2...v1.1.3
Hotfix v1.1.2
What's Changed
- Added fix for ctrl snapshot v1 log_logic by @bschlottfeldt in #103
- Added md5 binary support (Snowflake) by @tkirschke in #101
Full Changelog: v1.1.1...v1.1.2
v1.1.1
What's Changed
- Added datatype "ARRAY" for Ghost Records Snowflake by @JPLangner in #92
- Update hash_columns.sql by @tkirschke in #95
Full Changelog: v1.1.0...v1.1.1
v1.1.0
v1.1.0
New Features
- Reference Data: By adding new macros for Reference Hubs, Reference Satellites, and Reference Tables, datavault4dbt finally supports your reference data!
- Prejoining now supports other dbt Models: Instead of prejoining only with dbt sources, it now also supports other dbt models!
- Prejoin over multiple columns: The JOIN condition of a Prejoin can now be based on multiple attributes!
- Multi-Source entities can be loaded from different columns of the same source: Thanks to a changed metadata structure, multi-source entities can now be loaded out of different columns coming from the same source, as many times as you want it! Check this new wiki page for more details!
- Optional High-Water-Mark for Single-Source entities: When an entity is loaded only from one source, a High-Water-Mark is now enabled automatically without any additional config required! Thus, this can be disabled per model via a new parameter "disable_hwm".
- Performance Boost for NH-Links: Once you trust the staging data of a Non-Historized Link, you can now disable the de-duplication within the NH-Link laoding script to boost its performance!
- Deduplication in NH-Satellites: An optional QUALIFY statement is now added to NH-Satellites to support multi-batch processing. It can be disabled with a new parameter similar to NH-Links!
- v1 Satellites can exclude the payload: It is now possible to configure v1 Satellites to not again include the payload of the v0 Satellite!
Changes
- The hash method (based on the global variable hash) is now based on a new macro, similar to the macros of beginning_of_all_times and end_of_all_times.
Disclaimer
- All Changes and new Features are untested on Exasol! Due to licensing problems we were not able to test the Exasol Adapter macros, but this does not affect the other adapters!
Contributors
Hotfix v1.0.17
What's Changed
- Hotfix dbt packages by @tkirschke in #61
- Added robustability to Derived Columns datatype definition by @tkirschke in #65
Full Changelog: v1.0.16...v1.0.17
Hotfix v1.0.16
What's Changed
- Hotfix rsrs static query performance by @tkirschke in #58
Full Changelog: v1.0.15...v1.0.16
Hotfix v1.0.15
What's Changed
- Fix ghost records derived datatypes by @bschlottfeldt in #57
Full Changelog: v1.0.14...v1.0.15
Hotfix v1.0.14
What's Changed
- Fixed usage of zero keys in PIT macros for non-string datatypes by @tkirschke in #54
Full Changelog: v1.0.13...v1.0.14
v1.0.13 - Update in dependency
What's Changed
- Raised dbt_utils package requirements to <2.0.0 by @tkirschke in #55
- Allows users to bump their dbt_utils package to v1.0.0 which is the latest version available
Full Changelog: v1.0.12...v1.0.13