Release Notes

This page provides technical information about DataChain versions, migration procedures, and specific steps required for certain version upgrades. For functional evolutions, please refer to the functional release notes.

Version 8.7.0

Manual Update Procedures

Console and Marketplace Update

For users of beta console and marketplace versions, manual operations are required during migration. The data_view database and schema are replaced by marketplace database/schema, with renamed parameters for clarity.

Update procedure:

  • Stop non-database services

  • Backup databases

  • On data_view/marketplace database, do the following:

\c postgres
ALTER DATABASE data_view RENAME TO dc_marketplace;
\c dc_marketplace
ALTER SCHEMA data_view RENAME TO dc_marketplace;
UPDATE dc_marketplace.schema_changes SET checksum='-774607648' WHERE installed_rank=1;

  • On dc_console database:

\c dc_console
DELETE from dc_console.schema_changes WHERE version='1.1.1';

  • In marketplace (ex data_view) docker-compose file: rename image data_view to marketplace

  • In environment/docker-compose files: replace all dc.app.view parameters with dc.app.marketplace

  • If marketplace DB URL was overridden (via dc.app.marketplace.database.main-datasource), adapt URL to new database name. For example:

dc.app.marketplace.database.main-datasource.url=jdbc:postgresql://dc-pg:5432/dc_marketplace?prepareThreshold=0&preparedStatementCacheQueries=0&defaultRowFetchSize=1000

  • Deploy version 8.7.0

DataChain Core Update

One or more patches modify database structure. Verify migration service execution.

🚀 Technical Notes

New/modified API services for simplified interaction with connectors, repositories, and DataBlocks:

  • Duplicate project POST /service/projects/{id}/duplicate: Modified duplication service. Previously required full English consent text rewrite - now uses a boolean flag.

  • Check Connector connectivity POST /service/connectors/detailed/check_connection/{connectorId}: New generic connector validation service. ctx parameter optional.

  • Get connector by ID GET /service/connectors/detailed/{connectorId}: New connector details service using only ID (type no longer required).

  • List depots GET /service/depots: Modified service now returns project depots with their types.

  • Create Extraction POST /service/depots/detailed/{depotId}/extractions: New generic extraction creation using depot ID alone.

  • Get depot preview GET /service/depots/detailed/{depotId}/remote_file/preview: New preview service requiring only depot ID.

  • Execute DataBlock POST/service/datablock/exec_by_element_id: New execution service returning job key

  • Get execution results GET /service/datablock/exec/result/detailed: New service using job key to display detailed results

Version 8.6.0

One or more patches modify database structure. Verify migration service execution.

Spark container ports aligned with monitoring standards - Spark now listens on port 9090. Update Spark health checks in docker-compose and Traefik rules for actuator/monitoring access. Port list available here.

🚀 Technical Notes

Integration of information on:

Version 8.5.4

No additional technical information.

Version 8.5.3

Added PostgreSQL function. No data structure changes.

Version 8.5.2

No additional technical information.

Version 8.5.1

Database driver updates:

Database Type Version Comments

PostgreSQL

42.6.0

SQLServer

12.2.0

Oracle

19.22.0.0

Internationalization support (oraI18n)

MySQL

8.1.0

MariaDB

3.2.0

Version 8.5.0

Database migrations applied during installation. Verify patches success via migration logs.

Driver updates:

Database Type Version Comments

PostgreSQL

42.6.0

SQLServer

12.2.0

Oracle

19.19.0.0

Internationalization support (oraI18n)

MySQL

8.1.0

MariaDB

3.2.0

Version 8.4.0

Database migrations applied. Verify migration logs.
Added SMTP configuration parameters for deployment-level setup.

Version 8.3.1/8.3.2

No additional technical information.

Version 8.3.0

🚀 Technical Notes

Database Model

Database migrations applied. Verify patches success via migration logs.

Version 8.2.0

🚀 Technical Notes

During a new data exposure, the data to be replaced remains available for the duration of the exposure, to guarantee continued access to the data.

Database Model

Multiple database migrations applied. Verify patches success via migration logs.

Patches update exposure database. Verify pg_migration configuration. Configuration details here.