Skip to content

Releases: Datavault-UK/automate-dv

Version 0.7.6

14 Jul 08:49
Compare
Choose a tag to compare

[v0.7.6] - 2021-07-13

Documentation Status

  • Updated to dbt 0.20.0 and incorporated adapter.dispatch changes (#32)

THIS VERSION HAS A MAJOR BUG (#36) Please install v0.7.6.1, which contains a hotfix, as follows:

packages:
  - git: "https://github.com/Datavault-UK/dbtvault.git"
    revision: v0.7.6.1

Version 0.7.6-b1

11 Jun 18:04
Compare
Choose a tag to compare
Version 0.7.6-b1 Pre-release
Pre-release

THIS IS A BETA RELEASE

Whilst we have extensively tested this to the best of our ability, we cannot guarantee comprehensive coverage.

Please report any issues via GitHub, and feel free to ask us questions on Join our slack

Documentation is NOT complete, and improvements will be made before release. Thanks!


Documentation Status

New features:

To install:

Add the following to your packages.yml

packages:
  - git: "https://github.com/Datavault-UK/dbtvault"
    revision: 0.7.6-b1 #or release/0.7.6-b1

Version 0.7.5

10 Jun 20:18
Compare
Choose a tag to compare

[v0.7.5] - 2021-06-10

Documentation Status

New structures

Bug Fixes

  • Fixed a bug where an Effectivity Satellite with multiple DFKs or SDKs would incorrectly handle changes in the corresponding link records, meaning one to many relationships were not getting handled as intended.

Improvements

  • Added support for multiple order_by or partition_by columns when creating ranked columns in the stage or ranked_columns macros.
  • Performance improvement for the Satellite macro, which aims to reduce the number of records handled in the initial selection of records from the source data.

Version 0.7.4

28 Mar 00:08
Compare
Choose a tag to compare

[v0.7.4] - 2021-03-27

Documentation Status

Bug Fixes

  • Fixed NULL handling bugs in Hubs, Links and Satellites (#26)
  • Fixed a bug where Effectivity Satellites would incorrectly end-date (with auto-end-dating enabled) records other than the
    latest, resulting in duplicate end-date records for previously end-dated records.

Improvements

  • Added check for matching primary key when inserting new satellite records in the sat macro. This removes the requirement to
    add the natural key to the hashdiff, but it is still recommended. Read More

Quality of Life

  • Payload in Transactional (Non-Historised) links now optional
  • Effective From in Satellites now optional

Version 0.7.3

28 Jan 19:35
Compare
Choose a tag to compare

[v0.7.3] - 2021-01-28

Documentation Status

New

  • Updated dbt to v0.19.0
  • Updated dbt utils to 0.6.4

Version 0.7.2

26 Jan 11:30
Compare
Choose a tag to compare

[v0.7.2] - 2021-01-26

Documentation Status

New

  • Derived columns can now be provided lists, for creating composite column values. (#20)
    Docs

  • The hashed_columns exclude flag in staging can now be provided without a list of columns, and dbtvault will hash everything. Docs

  • Rank Load Materialisation: Iteratively load your vault structures over a configured ranking Read More

  • The stage macro now has a new ranked_columns configuration section to support the above materialisation. Read More

Improved

  • Optimised Satellite SQL for larger loads (billions) seen in the wild.
  • For non-hashdiff composite hashed_columns: If all components of the key are NULL, then the whole key will evaluate as NULL.
    Read more
  • Hashing concatenation now uses CONCAT_WS instead of CONCAT; this is more concise.
  • The stage macro has received a big overhaul, and the SQL should now be more efficient and easier to read.
  • Optimised table macro SQL across the board by reducing the number of CTEs

Fixed

  • Fixed multiple (minor) bugs in the stage macro (#21)
  • Fixed and improved the adapter.dispatch implementation (#22)
  • Fixed a bug in the vault_insert_by_period materialisation (#19)

Docs

Version 0.7.1

18 Dec 13:50
Compare
Choose a tag to compare

[v0.7.1] - 2020-12-18

Documentation Status

New

  • exclude_columns flag for hashdiffs - Inverse the columns selected for creating a hashdiff to select ALL columns except those listed in the metadata.
    This is very useful for large multi-column hashdiffs.
    See the new stage macro configurations section of the docs for more information.

Improved

  • The stage macro now generates CTE-based SQL instead of one big block. This makes it easier to read and debug.
    See here for more information on why we've moved to CTEs.

  • Multi-dispatch implementation now supports a package override variable, providing a smoother experience for
    users wishing to override macro implementations. Documentation will be made available in due course.
    See Issue #14 for more details.

  • Hashed columns now 'see' columns defined as derived columns. Allowing you to use them in your hashed column definitions.
    Issue #9
    See the new stage macro configurations section of the docs for more information.

Fixed

Version 0.7.0

25 Sep 17:53
a90f480
Compare
Choose a tag to compare

[v0.7.0] - 2020-09-25

Documentation Status

New

  • Effectivity Satellites: A newly supported Data Vault 2.0 structure.
    Read more
    Macro Reference

  • Period Load Materialisation: Iteratively load your vault structures over a configured period Read More

  • dbt Docs: The built-in dbt docs site (dbt docs serve) now includes documentation for dbtvault*.

  • dbt v0.18.0 support dbt v0.18.0 Release Notes

*This is intended as quick reference and for completeness only, the online documentation is still the main reference documentation.

Improved

  • All table macros now make more use of CTEs to reduce nested SQL and to improve readability and debugging potential. Why CTE's?
  • All macros have had the license header removed. This was a little messy and unnecessary.

Removed

Version 0.6.2

06 Aug 15:38
Compare
Choose a tag to compare

[v0.6.2] - 2020-08-06

Documentation Status

Fixed

dbt_project.yml

config-version: 1 caused an error in any dbt version prior to 0.17.x. We only put this config
in for users making use of variables in their dbt_project.yml file.

Note: If using vars in dbt_project.yml, you still need to specify config-version: 1 in your own project's dbt_project.yml.
Guidance will be released for alternatives to model-scoped dbt_project.yml vars in the next major release of dbtvault (0.7.x)

Read more about the config-version setting.

Version 0.6.1

24 Jun 16:57
Compare
Choose a tag to compare

[v0.6.1] - 2020-06-24

Documentation Status

Added

  • dbt 0.17.0 support
    WARNING This comes with a caveat that you must use config-version: 1 in your dbt_project.yml

  • All macros now support multiple dispatch. This update is to make way for additional platform support (BigQuery, Postgres etc.)

Changed

  • A hashdiff in the stage macro now uses is_hashdiff as a flag instead of hashdiff,
    this is to clarify this config option as a boolean flag.

Improved

Macros

  • Minor macro re-factors to improve readability

Removed

Macros

  • Cast macro (supporting) - No longer used.
  • Check relation (internal) - No longer used.