Release note - beVault 3.4

We are excited to announce the release of beVault Version 3.4! This version brings many different features in beVault.

Check out this release note to see what’s new and stay tuned for new incoming releases in 2025 🚀

Reference table

We added the possibility to create and map reference tables to store non-historized data, such as a list of countries or currencies.

Staging table v2

We completely reworked the visualization of the staging tables to improve the access to the metadata. The tab is now split into 3 different views, each one having its own purpose.

Metadata

This view allows you to quickly see and edit the metadata of the columns of your staging table.

Data

This view is similar to what we had in the past and still offers you the possibility to see the data in the modeling environment. This view can help you with the data profiling and to see the hard rules applied to real data.

Connections

This view allows you to quickly see the lineage of the staging tables. With this view, you can visualize to which entity your columns are mapped to. This is the first step to a global lineage feature to improve the auditability of your data.

IBM db2 support

beVault now supports IBM db2 as a target database for your Data Vault. You can now deploy your data model to your instance of IBM db2.

We also added a new data store for the workers to help loading data from your source systems to the staging area of the Data Vault thanks to the orchestrator of beVault, States.

List of changes

• Reference tables - Create non historized tables to store reference data

  • Source module - Possibility to map columns of a staging table to a reference table

  • Build module - Possibility to edit the metadata of a reference table

• Rework of staging table - to improve access to the metadata

  • Subdivided the staging table into 3 views

    • metadata

    • data

    • connections

  • Possibility to filter the columns available

  • Possibility to visualize the lineage between the staging table and the data model in the connections view

  • Rework of the mapping of the satellites

• Add IBM db2 support

  • Possibility to deploy the project to an IBM db2 database

  • Add a new data store “IBMdb2” for the workers

• Improved metadata in the meta schema

• Minor Bug fixing

Components' version

Configuration changes

datafactory-ui

Two docker compose environment variables have been added for Sentry session replays configuration

NG_APP_SENTRY_REPLAY_SAMPLE_RATE

Number value from 0 to 1.

Configures the percentage of session for which replays on error will be tracked.

NG_APP_SENTRY_REPLAY_MASK

Boolean value.

Configures whether the text and media should be masked on sessions replay.

metavault

S3/minio store for Metavault was removed, as well as the BulkImportExport worker. The DFAKTO_METAVAULT_FILESTORES_* variables are deprecated and will be ignored starting from this version. State machines trying to make use of the BulkImportExport worker of the metavault (the workers one remains in place, naturally) will hang forever as the worker does not exist anymore to handle the Task.

Instead, the corresponding functionalities of the Workers (https://dfakto.atlassian.net/l/cp/gsGuDgjy ) should be used.