Release note - beVault 3.6
We are excited to announce the release of beVault Version 3.6! This version brings small enhancements and fixes for the IBMdb2 support, as well as a new way to authorize users to connect to beVault on Snowflake environment.
Check out this release note to see what’s new and stay tuned for new incoming releases in 2025 🚀
List of changes
Metavault
Important: IBM db2 configuration changes (See: Supported target database configuration | IBM-Db2 for the engine-specific details)
The ORGANIZEBY Engine parameter is now explicit, you can choose between “Row” and “Column” and defaults to organization by “Row”. If you migrate from a 3.5 it is advised you set this to the default of your database, for consistency.
The COMPRESSION Engine parameter can be used to set compression modes on row-organized tables. Again, aligning with the defaults in your database is a good idea, since this is now explicit.
Add TABLESPACE Engine parameter which sets the tablespace for metavault-generated tables.
Add TABLESPACEINDEXES Engine parameter which sets the tablespace for metavault-generated table indexes.
Snowflake configuration changes (See: Supported target database configuration | Snowflake )
These are specifics to the deployment to Snowflake’s App store, and are likely best left turned off for regular deployments.
Bug fixes/ small improvements for IbmDb2
Reduce string length defaults to the lowest possible values (they are much smaller when using column-based, also they are specific to system page size, but that is hard to account for easily due to the structure of the engine)
Replaced CONCAT functions to use '||' instead, so that queries are more legible.
Disable generation of ALTER COLUMN and DROP COLUMN queries for columnar tables.
Set foreign keys to NOT ENFORCED for columnar tables.
Other improvements:
Possibility to add a list of additional valid issuers for JWT tokens. See: Metavault Configuration | Authentication
Possibility to remove to disable JWT (oidc)-based authentication, and use a HTTP header for user identification. (Again, this is mostly useful for Snowflake marketplace). See: Metavault Configuration | Authentication
Change the deployment of state machine to a background task to avoid timeout issues.
Workers
Add the possibility to change the encoding and the culture of the csv file generated by the ExportToCsv worker https://support.bevault.io/en/home/current/export-sql-query-result-to-csv
Components' version
Component | Version |
|---|---|
UI Version | 1.8.0 🆙 |
Metavault Version | 3.6.0 🆙 |
States Version | 2.2.0 🆙 |
States UI Version | 1.2.0 🆙 |
Workers Version | 1.9.0 🆙 |
Fix Versions
| Title | Release | Release Date | UI Version | Metavault Version | States Version | States UI Version | Workers Version | Summary |
|---|---|---|---|---|---|---|---|---|
| beVault release 3.6.4 | 3.6.4 |
| 1.8.0 | 3.6.4 | 2.2.1 | 1.2.0 | 1.9.1 | Improved database analysis during the deployment of a new version in an IBM db2 database |
| beVault release 3.6.6 | 3.6.6 |
| 1.8.0 | 3.6.6 | 2.2.1 | 1.2.0 | 1.9.1 | Fix an issue while deploying the meta schema with too large transformations on IBMdb2 |
| beVault release 3.6.5 | 3.6.5 |
| 1.8.0 | 3.6.5 | 2.2.1 | 1.2.0 | 1.9.1 | Fixed an issue appearing while renaming a hub or link |
| beVault release 3.6.3 | 3.6.3 |
| 1.8.0 | 3.6.3 | 2.2.1 | 1.2.0 | 1.9.1 | Fix a bug that removed the first line of an imported Excel file in IBMdb2 environment |
| beVault release 3.6.2 | 3.6.2 |
| 1.8.0 | 3.6.2 | 2.2.1 | 1.2.0 | 1.9.1 | Add the possibility to specify valid issuer’s URLs for authentication |
| beVault release 3.6.1 | 3.6.1 |
| 1.8.0 | 3.6.1 | 2.2.0 | 1.2.0 | 1.9.1 | Fix an issue with the connection pooling for IBMdb2 |
