DTLE 2.19.11.0 Release Notes – Features, Bug Fixes, and Version Highlights
The DTLE 2.19.11.0 release notes detail the project's purpose as a MySQL‑focused data transfer component, outline new features such as binlog relay and MySQL 8.0 support, list numerous bug fixes, and provide links to documentation and download resources for developers.
1. DTLE Project Introduction The open‑source DTLE component is designed for MySQL, offering reliable cross‑data‑center transfer, cloud‑to‑cloud synchronization, data aggregation, subscription to Kafka, and bidirectional replication to address quality, complexity, and functionality needs.
2. Version Features
Relay of binary logs (#475) – DTLE downloads binlog from source MySQL to local storage to handle PURGE BINARY LOGS on the source.
Support for starting incremental jobs with binlog file and position (without GTID).
New job.json options: BinlogRelay , BinlogFile , BinlogPos – preliminary support for MySQL 8.0 (#487).
Log system enhancements: dynamic log‑level changes, updated log format, and log file rotation.
3. Bug Fixes
Job API now returns the reason after a job dies.
Corrected erroneous increment of BinlogEntrySize (#499).
Fixed failures caused by empty NATS (#433).
Resolved crashes when tables lack primary keys (#488), contain special characters (#476), or have schema‑table mapping issues (#481).
Addressed job stalls in the incremental stage (1bee6d31).
4. Release Notes Summary
The release adds Binlog Relay, enhances binlog handling, introduces new job configuration options, improves log management, and fixes critical bugs affecting job stability and compatibility with MySQL 8.0.
For more details, see the official project repository https://github.com/actiontech/dtle , documentation https://actiontech.github.io/dtle-docs-cn/ , and download the latest tarball from the releases page.
Aikesheng Open Source Community
The Aikesheng Open Source Community provides stable, enterprise‑grade MySQL open‑source tools and services, releases a premium open‑source component each year (1024), and continuously operates and maintains them.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.