DTLE 2.19.05.0 Release Notes – Project Overview, Feature Improvements, and Bug Fixes
The DTLE 2.19.05.0 release notes introduce the enterprise‑grade open‑source distributed data‑transfer component, detail a new job‑failure hint feature, and enumerate several bug fixes including table‑name case handling, mapping job failures, Docker startup issues, and Kafka unknown table structures.
DTLE (Data‑Transformation‑le) is an enterprise‑grade open‑source distributed data‑transfer component that supports MySQL full and incremental replication, bidirectional replication, database aggregation, table conversion, and data subscription, with capabilities for multi‑scenario network adaptation, cloud‑to‑cloud migration, and cross‑data‑center synchronization.
Official project repository: https://github.com/actiontech/dtle . Installation documentation can be found at https://actiontech.github.io/dtle-docs-cn , and releases are available at https://github.com/actiontech/dtle/releases .
Feature Improvement
Improved job‑A: the system now provides a reason after a job dies, adding a prompt when the DTLE API reports a dead job.
Bug Fixes
Table name case problem #441‑1 – fixed errors caused by automatic conversion to lowercase.
Use mapping job.json failed when testing increment, the job is 'complete' #447 – resolved the 'complete' status issue during mapping incremental tests.
After job creation, inserting data to null schema in source caused DTLE panic #450 – fixed panic when inserting empty data into source.
Mapping: after renaming, deleting source table, destination table not deleted #453 – ensured destination tables are removed when source tables are deleted after a rename.
Docker run failed to start #454 – resolved Docker startup failure.
Kafka: unknown table structure #459 – fixed errors when Kafka encounters unknown table structures during transfer.
DTLE 2.19.05.0 is an optimization release that addresses a batch of bugs and introduces minor usability enhancements.
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.