Releases: Datavault-UK/automate-dv
Version 0.6
[v0.6] - 2020-05-26
MAJOR UPDATE
We've added a whole host of interesting new features.
Read our v0.5 to v0.6 migration guide
Added
-
Staging has now been moved to YAML format, meaning dbtvault is now entirely YAML and metadata driven.
See the new stage macro and the staging tutorial for more details. -
Renamed
source
metadata configuration tosource_model
to clear up some confusion.
A big thank you to @balmasi for this suggestion. -
HASHDIFF
aliasing is now available for Satellites
Read More
Upgraded
- hub and link macros have been given a makeover.
They can now handle multi-day loads, meaning no more loading from single-date views.
We'll be updating the other macros soon, stay tuned!
Fixed
- Fixed
NULL
handling when hashing. We broke this in v0.5 (see related issue)
Read more
Removed
- Deprecated macros (old table template macros)
- A handful of now unused internal macros
- Documentation website from main repository (this makes the package smaller!)
New docs repo
Version 0.6 beta 2
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
Version 0.4.1
Version 0.4
[v0.4] - 2019-11-27
That''s right, we're finally out of pre-release!
Added
- Table Macros:
Improved
- Hashing:
- You may now choose between
MD5
andSHA-256
hashing with a simple yaml configuration
Learn how!
- You may now choose between
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
Pre-Release v0.3.2
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