DBConvert Streams releases in 2024. #

Version 0.11.2 #

📆 May 15, 2024

Bug Fixes: #

1. Fix MySQL datetime default value parsing

• Addressed the issue where the default value for MySQL datetime(6) columns was not being parsed correctly when migrating to PostgreSQL. This resolves the error: "invalid input syntax for type timestamp: "CURRENT_TIMESTAMP(6)" (SQLSTATE 22007)".

2. Fix conversion of bit data type from MySQL to PostgreSQL

• Resolved the issue where the bit data type from MySQL was not being correctly converted to PostgreSQL's boolean type. This fix addresses the error: "column "col2" is of type boolean but default expression is of type bit (SQLSTATE 42804)".

New Features #

Implement migration of geospatial Point type from MySQL to PostgreSQL

• Added support for migrating the MySQL POINT data type to PostgreSQL's geometry type. This new feature resolves the error: "unknown colType POINT".

For more details and the original issue discussion, please refer to https://github.com/slotix/dbconvert-streams-public/issues/36.

For more information and to download the latest version, please visit our website or contact our support team.

Visit the DBConvert Streams Docker Guide for detailed instructions on setting up and running DBConvert Streams in a Docker environment.

We are committed to continually improving DBConvert Streams to provide users with a reliable and efficient data migration solution. Thank you for your continued support and feedback.

Version 0.10.16 #

📆 April 29, 2024

Bug Fixes: #

1. Fixed Issue with BINARY Column Data Type Conversion: We've resolved an issue encountered when creating table structures containing BINARY column data type from MySQL on the Postgres target. For more information, please refer to GitHub issue #31.

2. Improved Accuracy in Average Rate Calculation: We've enhanced the accuracy of average rate calculation in scenarios where the elapsed time is less than 1 second. With this fix, users can rely on more precise performance metrics, ensuring accurate analysis and optimization of data transfer processes.

3. Resolved Enum Data Type Conversion Issue: This update addresses an issue related to converting enum data type from MySQL to Postgres. For more information, please refer to GitHub issue #32.

For more information and to download the latest version, please visit our website or contact our support team.

Version 0.10.12 #

📆 April 9, 2024

Features: #

1. Index Existence Handling: Enhanced functionality to manage cases where the index already exists in the target database. This feature ensures smoother data migration processes by effectively addressing potential conflicts.

2. Table Structure Notification: Implemented a mechanism where the target writers notify the source reading service regarding the status of creating table structures on the target db. This ensures better coordination and visibility during the data transfer process.

3. Logger Output Enhancement: Improved the output format of loggers to enhance the visual representation of statistics. The updated output provides clearer insights into the performance and status of the migration process, aiding in comprehensive data analysis and troubleshooting.

Version 0.10.9 #

📆 March 2, 2024

New Features #

1. Log-Level Flag for Services
   • Introducing a new log-level flag for services to provide greater flexibility in logging configurations. Users can now specify the debug log level for each of DBConvert Streams service, allowing for more fine-grained control over the verbosity of logs.

Bug Fixes #

1. Improved Handling of Service Statuses during Database Operations

   • Resolved an issue related to the handling of services statuses during the creation of tables and indexes on the target database. Users can now expect more accurate and reliable service status updates during these database operations.

2. Fixed Year Type Handling for MariaDB to PostgreSQL Migration

   • Addressed a specific issue in the migration process from MariaDB to PostgreSQL where the handling of year type data was not accurate. The migration now correctly interprets and transfers year type data, ensuring data integrity and consistency between the two database systems.

Version 0.10.7 #

📆 February 28, 2024

Table Structure Creation Handling: #

A notable improvement has been implemented to handle cases where a writer instance tries to insert data before the target table structure is established on the destination database.

The target writer, responsible for creating table structures, now notifies other target writer instances upon the successful completion of the structure creation process.

Version 0.10.6 #

📆 February 22, 2024

1. Improved Error Handling: In this release, we've refined the processing mechanism to handle indexes one by one. This enhancement ensures better error handling throughout the processing pipeline.
2. Enhanced Logging Errors and Warnings: We recognize the critical nature of migrating tables and index structures across diverse database types. With this release, our logging capabilities have been substantially bolstered. You can now expect more detailed information about potential issues related to the database engine.
3. Date Field Conversion Fix: We've addressed a critical issue related to date fields containing values like "0000-00-00" during the conversion from MySQL to Postgres. The fix ensures accurate and seamless conversion, preventing any inconsistencies in the date values.

Version 0.10.3 #

📆 February 14, 2024

Features and Fixes #

1. Fix Parsing Time Field Types on Target

   • Resolved issues related to parsing time field types on the target database, ensuring accurate data conversion.
   • Issue #24: convert from MySQL YEAR field type to PostgreSQL has been resolved.

2. Fix Stream Stopping Issue with "Ghosted" Nodes

   • Addressed a critical issue where the stream erroneously stopped when the target status was 'failed.' This fix ensures proper handling of failed targets and avoids the creation of ghost nodes that hinder subsequent stream initiation.

3. Handle Error When Retrieving Stats from Nodes with No Active Stream

   • Implemented error handling to manage situations where stats are retrieved from nodes without an active stream.

4. Fix Full-Text Search Index Type Conversion from MySQL to Postgres

   • Corrected the conversion of full-text search index types from MySQL to Postgres, ensuring accurate and consistent indexing.

5. Implement Options for Target Database

   • Introduced options for the target database, offering enhanced control over behavior during data conversion and loading. Refer to the target configuration documentation for detailed descriptions of available options.

6. Fix Data Races

   • Addressed data race issues to enhance the stability and reliability of DBConvert Streams.

7. Refactor Logger and Publish Log Messages to NATS Stream

   • The logger has been refactored, and log messages are now can be published to NATS Stream.

Download the latest binaries from:

Version 0.9.1 #

📆 January 12, 2024

This release brings important improvements and bug fixes to enhance your experience with Postgres CDC (Change Data Capture). Below are the key highlights of this release:

Features and Enhancements: #

1. Postgres CDC: Support for Version 2 Protocol
   • In this release, we have introduced support for the Version 2 protocol for streaming large transactions in Postgres CDC. This enhancement ensures smoother and more efficient handling of substantial data changes, providing a more robust and reliable CDC experience.

Bug Fixes: #

1. Postgres Source Reader in CDC Mode
   • Addressed an issue where the Postgres source reader, when started in CDC mode, sometimes failed to detect incoming events. This bug has been fixed, ensuring that the CDC functionality now consistently captures and processes all relevant changes from the source.

Version 0.9.0 #

📆 January 08, 2024

Improvements #

Publish Stop Status via NATS #

• In this release, we've implemented a more efficient mechanism for handling stop status updates. Instead of directly calling services through the API endpoint, the stop status is now published via NATS. This not only resolves the issue with stopping current stream processing but also ensures a more reliable and real-time communication channel.

Simplify Functions for Streaming Databases #

• We've streamlined the process of streaming data between MySQL and PostgreSQL databases. The functions for these operations have been simplified, making the overall experience more user-friendly and efficient.

Enhance Output from Statistics Endpoint #

• The statistics endpoint has been enhanced to provide more accurate and real-time information. Service instances now report their states to NATS, and when the API polls these instances, the information is retrieved in a structured JSON format. This improvement ensures a dynamic and responsive system for better monitoring and analysis.
  • Find more information about this enhancement at GitHub Issue #18.

Bug Fixes #

• Fixed an issue with stopping current stream processing from the API endpoint. (Issue #13)
  • This bug was reported and addressed in GitHub Issue #13.