Releases · yugabyte/yb-voyager

v1.7 - May 16, 2024

Assess Migration [TECH PREVIEW] (for PostgreSQL source only): Introduced the Voyager Migration Assessment feature specifically designed to optimize the database migration process from various source databases, currently supporting PostgreSQL to YugabyteDB. Voyager conducts a thorough analysis of the source database by capturing essential metadata and metrics, and generates a comprehensive assessment report.
- The report is created in HTML/JSON formats.
- When export schema is run, voyager automatically modifies the CREATE TABLE DDLs to incorporate the recommendations.
- Assessment can be done via plain bash/psql scripts for cases where source database connectivity is not available to the client machine running voyager.
Support for live migration with the option to fall-back for PostgreSQL source databases.
Support for live migration of partitioned tables and multiple schemas from PostgreSQL source databases.
Support for migration of case sensitive table/column names from PostgreSQL databases.
- As a result, the table-list flags in import data/export data can accept table names in any form (case sensitive/insensitive/quoted/unquoted).

Detect and skip (with user confirmation) the unsupported data types before starting live migration from PostgreSQL databases.
When migrating partitioned tables in PostgreSQL source databases, voyager can now import data via the root table name, making it possible to change the names or partitioning logic of the leaf tables.

Workaround for a bug in YugabyteDB where batched queries in a transaction were internally retried partially without respecting transaction/atomicity semantics.
Fixed a bug in export data (from PostgreSQL source databases), where voyager was ignoring a partitioned table if only the root table name was specified in the --table-list argument.
Fixed an issue Voyager was not dropping and recreating invalid indexes in case of restarts of 'post-snapshot-import' flow of import-schema.
Fixed a bug in analyze schema that reports false-positive unsupported cases for "FETCH CURSOR".
Changed the datatype mapping of DATE:date to DATE:timestamp in Oracle to avoid time data loss for such columns.
Increased maximum retry count of event batch to 50 for import data streaming.
Fixed a bug where schema analysis report has an incorrect value for invalid count of objects in summary.

If you use dockerised version of yb-voyager, commands get data-migration-report and end migration do not work if you have previously passed ssl-cert/ssl-key/ssl-root-cert in export data or import data or import data to source replica commands.

Support for live migration from PostgreSQL databases with the option of fall-forward, using which you can switch to a source-replica PostgreSQL database if an issue arises during migration [Tech Preview].

The live migration workflow has been optimized for Importing indexes and triggers on the target YugabyteDB. Instead of creating indexes on target after cutover, they can now be created concurrently with the CDC phase of import-data-to-target. This ensures that the time consuming task of creating indexes on the target YugabyteDB is completed before the cutover process.
The --post-import-data flag of import schema has been renamed to --post-snapshot-import to incorporate live migration workflows.
Enhanced analyze schema to report the unsupported extensions on YugabyteDB.
Improved UX of yb-voyager get data-migration-report for large set of tables by adding pagination.
The YugabyteDB debezium connector version is upgraded to v1.9.5.y.33.2 to leverage support for precise decimal type handling with YugabyteDB versions 2.20.1.1 and later.
Enhanced export data status command to report number of rows exported for each table in case of snapshot-only migration.
Reduced default value of --parallel-jobs for import data to target YugabyteDB to 0.25 of total cores (from 0.5), to improve stability of target YugabyteDB.

Fixed a bug in the CDC phase of import data where parallel ingestion of events with different primary keys having same unique keys was leading to unique constraint errors.
Fixed an issue in yb-voyager initiate cutover to target where fallback intent is stored even if you decide to abort the process in the confirmation prompt.
Fixed an issue in yb-voyager end migration where the source database is not cleaned up if --save-migration-reports flag is set to false.
yb-voyager now gracefully shuts down all child processes on exit, to prevent orphan processes.
Fixed a bug in live migration where "\r\n" in text data was silently converted to "\n". This was affecting snapshot phase of live migration as well as offline migration with BETA_FAST_DATA_EXPORT.