Version 0.6 beta 2

[v0.6 beta 2] - 2020-04-15

THIS IS A BETA RELEASE, USE WITH CARE

• Improvements to effectivity satellites
• Added more documentation for effectivity satellites
• Fixed more macro headers (removed copyright etc.)
• Improved Link macro to work with effectivity satellites

Version 0.5

[v0.5] - 2020-02-24

Added

• Metadata is now provided in the dbt_project.yml file. This means metadata can be managed in one place.
  Read Migrating from v0.4 to v0.5 for more information.

Removed/Deprecated

• [Deprecated] Target column metadata mappings are no longer required
• [Deprecated] Manual column mapping using triples to provide data-types and aliases (messy and bad practice).
• [Removed] copyright notice from generated tables (we are open source, duh!)

Fixed

• Hashing a single column (using the hash macros) which contains a NULL value now works as intended.

Version 0.6 beta 1

[v0.6 beta 1] - 2020-04-06

Added

• Support for dbt version 0.16.0
• Effectivity Satellites - Basic documentation available, more to come soon!

Version 0.4.1

[v0.4.1] - 2020-01-08

Added

• Support for dbt v0.15

Version 0.4

[v0.4] - 2019-11-27

That''s right, we're finally out of pre-release!

Added

• Table Macros:
  • Transactional Links

Improved

• Hashing:
  • You may now choose between MD5 and SHA-256 hashing with a simple yaml configuration
    Learn how!

Worked example

• Transactional Links
  • Added a transactional link model using a simulated transaction feed.

Documentation

• Updated macros, best practices, roadmap, and other pages to account for new features
• Updated worked example documentation
• Replaced all dbt documentation links with links to the 0.14 documentation as dbtvault
  is using dbt 0.14 currently (we will be updating to 0.15 soon!)
• Minor corrections

Pre-Release v0.3.3

[v0.3.3-pre] - 2019-10-31

Documentation

• Added full demonstration project/worked example, using the Snowflake TPC-H dataset.
• Minor corrections

Pre-Release v0.3.2

[v0.3.2-pre] - 2019-10-28

Bug Fixes

• Fixed a bug where the logic for performing a base-load (loading for the first time) on a union-based hub or link was incorrect, causing a load failure.

Documentation

• Various corrections and clarifications on the macros page.

Pre-Release v0.3.1

[v0.3.1-pre] - 2019-10-25

Error handling

• An exception is now raised with an informative message when an incorrect source mapping is
  provided for a model in the case where a source relation is also provided for a target mapping.
  This caused missing columns in generated SQL, and a misleading error message from dbt.

Pre-Release v0.3

[v0.3-pre] - 2019-10-24

Improvements

• We've removed the need to specify full mappings in the tgt metadata when creating table models.
  Users may now provide a table reference instead, as a shorthand way to keep the column name
  and date type the same as the source, read the docs for more details.
  The option to provide a mapping is still available.

• The check for whether a load is a union load or not is now more reliable.

Documentation

• Updated code samples and explanations according to new functionality
• Added a best practises page
• Various clarifications added and errors fixed

Pre-Release v0.2.4

[v0.2.4-pre] - 2019-10-17

Bug Fixes

• Fixed a bug where the target alias would be used instead of the source alias when incrementally loading a hub or link, causing subsequent loads after the initial load, to fail.