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

• bschlottfeldt
• tkirschke

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

Hotfix v1.0.12

What's Changed

• Fixed "48 hash datatypes other than string cause an error" by @tkirschke in #52
• Fixed wrong "is_weekly" in snap_v0 for Snowflake by @tkirschke in #51

Full Changelog: v1.0.11...v1.0.12

Contributors

@mjahammel Thanks for finding both issues!

Hotfix v1.0.11

Bugfixes (all adapters)

• concattenated_standardise & multi_active_concattenated_standardise: The check for alias was not yet implemented in the Snowflake and default versions of the macro concattenated_standardise and multi_active_concattenated_standardise.
• concat (Snowflake) : replaces the single quote in the CONCAT() of Snowflake that was generating a formatting problem in VS Code, with double quote.

Contributors:

• @bschlottfeldt

Hotfix v1.0.10

Bugfixes (all adapters)

• PIT: When users would select satellites without load-end-dates as the tracked satellites for a PIT, the LEFT JOIN to that satellite has not worked. This is now fixed and the determination of the respective active record is done via generating a virtual load-end-date in-between.

Contributors

• @obause: Bug finding & -fixing on all adapters + Testing on Snowflake
• @bschlottfeldt : Testing on Exasol
• @tkirschke: Testing on BigQuery

Hotfix v1.0.9

Bugfix (all adapters)

• Stage: There was a problem with the previous fix in the Stage macro dispatching file, even when setting in the model the include_source_columns as false it was resetting it as true because of the logic inside the macro is_something. To check now if it is passed as empty the if statement now checks if the variable is none or if it is equal to an empty string.

New feature (all adapters)

• PIT: Added a DISTINCT to the select statement in records_to_insert CTE to remove duplicate rows originated from using PIT table on Multi-active satellites. This feature allows supporting the SMA (created with our ma_sat_v1 macro) in PIT tables, as well as non-historized satellites and normal satellites.

Contributors

• @bschlottfeldt