DTLE Open‑Source Data Transfer Middleware 2.19.03.0 Release Highlights
The DTLE 2.19.03.0 release introduces cross‑data‑center transfer, cloud synchronization, data aggregation, DDL filtering, schema name conversion, and numerous bug fixes, providing a reliable MySQL‑focused middleware for diverse data replication and migration scenarios.
On April 9, the open‑source data transfer component DTLE released version 2.19.03.0. DTLE is designed for MySQL, supporting various scenarios to ensure reliable data transmission, adapt to complex environments, and provide diverse functions.
Core application scenarios include cross‑data‑center transfer, cloud‑to‑cloud synchronization/migration, data aggregation, data subscription (e.g., publishing changes to Kafka), and bidirectional replication across data centers.
New version features: fine‑grained DDL filtering, enhanced DDL handling with in‑memory schema computation, an alpha feature for schema/table name conversion, plus numerous fixes for job status handling, temporary table sessions, binlog thread detection, systemd start failures, and primary‑key selection for paging.
The release also addresses specific community‑reported issues such as job failures, primary‑key replay, and systemd service start problems.
Download the latest binaries at https://github.com/actiontech/dtle/releases , view the Chinese PDF documentation at https://actiontech.github.io/dtle-docs-cn/ , and join the QQ technical support group (852990221).
For more details, refer to the full release notes and online documentation; users are encouraged to read the original GitHub release page.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
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.
