DTLE 4.22.11.0 Release Notes – New Features, Configuration Changes, and Bug Fixes
DTLE 4.22.11.0 introduces major job configuration changes, new log settings, a TwoWaySync parameter for bidirectional replication, beta Kafka credentials, and fixes for Decimal column defaults, while providing updated documentation links and download resources for the open‑source MySQL data transfer component.
DTLE 4.22.11.0 Release Notes
The open‑source DTLE project, a MySQL‑focused data transfer component, has released version 4.22.11.0. The source code, documentation, and release information are available at the GitHub repository and official docs.
Important Changes
Job configuration method has been changed and is not compatible with previous configurations; all configuration items have moved to src task .
ConnectionConfig has been renamed to SrcConnectionConfig or DestConnectionConfig .
Destination task now has a single configuration item: DestType = "mysql" # or kafka .
Refer to /usr/share/dtle/example.job.hcl and the job configuration documentation for details.
Log handling is now independent: a new log_file configuration item is added, and the process for adjusting log_level has been simplified.
New Features
Added job parameter TwoWaySync to enable single‑job bidirectional replication, avoiding potential circular copy issues.
(Beta) Added Kafka parameters User and Password (issue #968).
Bug Fixes
Fixed an error when a Decimal column had a default value (issue #1032).
Recommended reading includes articles on enabling HTTPS access for DTLE, syncing MySQL to DBLE, configuring failover domains, and performance testing of parallel replay.
For more information, visit the official documentation, GitHub releases page, or join the community QQ group (852990221).
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.