---
title: "2022"
canonical: "https://docs.vaultspeed.com/space/VPD/3364389027/2022"
format: markdown
---
**Table of Contents**

> Macro (toc)

### Version 5.2.1

Release date: 28/10/2022

- Features:
  - Added support for **SingleStore **as a new target technology

> ℹ️ Automatic deployment of code to SingleStore does require an update to the VaultSpeed agent. The standard update procedure can be found here: ​[https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3081306131](https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3081306131) ​

> ℹ️ Running code on SingleStore using Airflow does require an update to the VaultSpeed Airflow Plugin. You can download the latests version of the plugin from the VaultSpeed application in the FMC menu. Installation instructions can be found in [https://vaultspeed.atlassian.net/wiki/pages/createpage.action?spaceKey=vpd&title=Airflow%20Installation%20Instructions&linkCreation=true&fromPageId=3364389027](https://vaultspeed.atlassian.net/wiki/pages/createpage.action?spaceKey=vpd&title=Airflow%20Installation%20Instructions&linkCreation=true&fromPageId=3364389027)

### Version 5.2.0

Release date: 11/09/2022

> ℹ️ This release contains changes to the VaultSpeed Agent, so it should be updated. The standard update procedure can be found here: ​[https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3081306131](https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3081306131) ​

- Features:
  - Added support for creating **multiple layers** with the **VaultSpeed Studio**. A studio template can now be built on top of another template. It is also possible to define extra layers after the business vault where the objects resulting from these templates can be stored. For more details and examples go to [https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3010363474](https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3010363474) .
  - Added support for **Denodo **views. When enabled, VaultSpeed will generate wrapper views in Denodo which reference the Raw Vault objects.  
It is then also possible to generate new Denodo views from VaultSpeed Studio templates. Documentation is available here: [https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3291447886](https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3291447886) .
  - **Agent connections** can now be **stored **more **securely**. We have added support for storing the connections in Azure Key Vault, Java Key store, and a directory with a file per connection.  
For more information and setup instructions go to [https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3291381934](https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3291381934).
  - Added support for creating **empty hub groups**. This can be useful when using the API to create HUB groups based on a conceptual data model, before adding sources that will provide the objects that need to fill that HUB. An example of such an import from Ellie was posted on our community [VaultSpeed Community](https://community.vaultspeed.com/ellie-sp1l18bx/post/ellie-to-vaultspeed-api-integration-experience-NZ4H0mTdnbEY57P). (When you get a post-no-found notification, you can go to [https://community.vaultspeed.com](https://community.vaultspeed.com/), register, navigate to the Ellie channel, and join the channel if needed)
  - Added **Record Tracking Satellites**(RTS), for No CDC objects, a new object parameter `ADD_RECORD_TRACKING_SATELLITE` can be enabled. This will attach an RTS object on its HUB, which will keep track of which keys existed in each load. Based on the data in this object, business rules could distinguish between a record that was not loaded due to a lock in the source and a true delete.
  - The **beta release** of our **updated UI** is available. We have added buttons to easily switch between the 2 versions of the UI. More info here: [https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3291382014](https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3291382014)   
The new UI has a bunch of improvements:
    - Updated look and feel
    - Better performance
    - Color themes
    - Better pagination
    - Better navigation
    - URLs contain more information, meaning that you can now have an URL pointing to the source editor of a specific release.
    - Editing is now done through a new actions menu instead of by double-clicking.
- Important changes:
  - Added support for hard deletes to ODI generations.
  - The Firewall logic was removed, it could lead to some incorrect detections when using intra-loadcycle changes. To avoid loading the same records twice, use our table-specific loading window logic. The DFV-views will still be there, but now only contain the delta-logic.

- Quality of life changes:
  - Added the filter expression from a source object split to the metadata export and added the original source object name in src_linked_table instead of the split.
  - Added ddl options for FMC & MTD tables.
  - Added specific DDL options for drop table statements (these might be needed when trying to drop external tables). VaultSpeed will automatically generate a default preset for Postgres and Snowflake containing a “CASCADE”.
  - Added the correct data types when entering attributes in the expression editor for a source object split filter.
- Bug fixes:
  - Fixed missing dependencies between HUB and STG in Airflow DAGs for early arriving facts.
  - Added a check to prevent the creation of multiple Data Vaults with the same name, the code can be the same for multiple DVs.

### Version 5.1.0

Release date: 15/05/2022

> ⚠️ The VaultSpeed Airflow integration with Snowflake has changed. If you use Snowflake as a target you should update the plugin before generating new flows. [https://vaultspeed.atlassian.net/wiki/pages/createpage.action?spaceKey=vpd&title=Airflow%20Installation%20Instructions&linkCreation=true&fromPageId=3364389027](https://vaultspeed.atlassian.net/wiki/pages/createpage.action?spaceKey=vpd&title=Airflow%20Installation%20Instructions&linkCreation=true&fromPageId=3364389027)

> ℹ️ This release contains changes to the VaultSpeed Agent, so it should be updated. The standard update procedure can be found here: ​[https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3081306131](https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3081306131) ​

- Features:
  - The VaultSpeed** API** is out of closed beta and is now available for everyone. More information and an example can be found at [https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3011936280](https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3011936280).
  - New **CDC** type: **Modification Sequence**, if a source/object delivers changed records with a sequence number indicating the order of changes, then this new CDC type can be used together with CDC_BASED_LOADING_WINDOW to only load new changes by keeping track of the last loaded sequence number. More info can be found at [https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3081633856](https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3081633856) .
  - Added support for Using **Azure Data Factory** as the FMC for **Databricks**. To get started, take a look at the documentation: [https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3164635181](https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3164635181). This requires an update of the VaultSpeed Agent!
  - Introducing the **Source Object Splitter**, this is a powerful new addition to the source editor** **which allows you to split a source object into multiple objects, each with a subset of the attributes and possibly a filter expression. For more details and example use cases, go to [https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3163914550](https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3163914550).
- Important changes:
  - Introduced a rate limiter for the VaultSpeed API.
  - Added support for executing Spark SQL code with Apache Livy from Airflow. The connection for Spark SQL can now be 3 different types: Spark CLI, JDBC, or Livy.  
Configuration instructions can be found in the documentation: [https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3038412824](https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3038412824).
- Quality of life changes:
  - All documentation links in the app have been updated to point to the new documentation location: [docs.vaultspeed.com](http://docs.vaultspeed.com/).
  - Performance improvements for the source editor.
- Bug fixes:
  - Fixed an issue in the Agent where, when executing some tasks for the first time, a warning from SLF4J would appear in the log.
  - In the DDL generation, the “EXTERNAL” keyword was missing from the drop statements when it was added as a DDL option.
  - Fixed an issue causing the order of the other attributes in a REF object to be different from the attribute order in the source.
  - Fixed an issue where, in the source editor, an attribute was tagged as being a PK even though the actual constraint was disabled.

### Version 5.0.0

Release date: 23/02/2022

> ⚠️ The VaultSpeed Airflow plugins JdbcToJdbcTransfer Operator (used for source loading) has changed. If you use source loading you should update the plugin before generating new flows. Also all existing flows which use source loading have to be regenerated after updating the plugin.

> ℹ️ This release contains changes to the VaultSpeed Agent, so it should be updated. The standard update procedure can be found here: [https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3081306131](https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3081306131)

- Features:
  - Added **Spark Structured Streaming** support. There is a new source parameter STREAMING_SOURCE which indicates that the source should be loaded by streaming instead of with a batch load. The other sources in your Data Vault can still be loaded in batches. At the moment, only Kafka is supported as a source stream. The target technology can be anything. If the target is not Spark, then our streaming solution will write the data to the target platform using JDBC. The only Spark Streaming platform that is supported at the moment is Databricks. The VaultSpeed streaming solution is robust to referential integrity issues. It contains logic to resolve short-term problems like latency and long-term issues like missing keys in the source system or downtime. This is currently a beta release so there can still be issues. Streaming is a separate subscription package and is only available for platinum customers.
  - **Object-specific** and **CDC-based loading window**: These two new parameters improve the logic behind calculating the loading windows by the FMC. The OBJECT_SPECIFIC_LOADING_WINDOW parameter will ensure that each source object has its own loading window and should be used in combination with FMC_DYNAMIC_LOADING_WINDOW. The CDC_BASED_LOADING_WINDOW parameter will cause the end date of the loading window to be determined by the maximum available CDC timestamp of the object. This ensures that all data gets loaded, providing that it arrives in chronological order. It can resolve syncing issues between CDC data delivery to the target and the loading schedule.
  - Added support for **INSERT_ONLY=N** with merges for **Databricks**.
- Important changes:
  - Introduced a new hashing algorithm: “No hash”, this will not hash anything and instead leave the input as a concatenated string.
  - Added a page in the UI containing the API documentation. It includes automatic authentication meaning that the endpoints can be immediately called from the UI to test them out. Note that this is only accessible for customers with API access.
  - Added support for username and password authentication to the GIT deploy.
- Quality of life changes:
  - The parameter: CLOSE_DELETED_RECORDS has been moved from the system level to the object level.
  - Added error codes in the API to indicate when an endpoint is not available for your subscription. For example, the FMC endpoints when the FMC is not part of the subscription.
  - Added an option to hide VaultSpeed Studio previews from the list of the generations on the Auto Deploy screen.
  - Changes to the metadata export:
    - Added “source”: same as “src_name”, which will be deprecated in the future.
    - Added “source_name”: name of the source (instead of a combination of the source name and release info in “source”).
    - Added “src_linked_table”: This attribute contains the source table name of the object referenced by a foreign key attribute.
    - Added “src_linked_column”: This attribute contains the source column name of the primary key attribute referenced by a foreign key attribute.
    - Added “dv_linked_hub_name”: This attribute contains the referenced HUB name for Foreign Hash Key attributes in link tables.
    - Updated “src_name_in_bk”: This now returns the full source business key, so including the object name when there is an inter source hub group.
  - Added the possibility to delete FMC workflows.
  - Updated the Snowflake JDBC Driver in the agent to the latest version.
  - Added a new Hive JDBC Driver in the agent, this will also significantly reduce the size of the agent package.
  - Updated Airflow FMC generation to use the new name for the BigqueryOperator.
  - It is now possible to deploy the DDL code to Databricks as a Notebook, instead of just executing it.
- Bug fixes:
  - Fixed an issue with the initial load for many-to-many links where if there are records that reference only unknown records, then it could cause conflicts with the ghost records in some parameter combinations.
  - Fixed the ordering of old DV releases in the delta generation screen.
  - Fixed connection info from the agent being shown in the UI when there was an error retrieving the connection from the properties file. This could show password details from the connection definition. The info will no longer be shown in either the agent log or the VaultSpeed application.
  - Fixed an issue with the EXT initial load mapping for Talend on Postgres version 9.6 or lower.
  - Fixed an issue where a manually defined foreign key could not be disabled if the primary key it referenced was deleted in the source.
  - Fixed exit 0 statement not getting generated for snapshot date views for PIT's in oracle SQL.