Skip to main content
Version: 4.x

TapData Enterprise Release Notes

Applicable EditionsTapData EnterpriseTapData Enterprise can be deployed in your local data center, making it suitable for scenarios with strict requirements on data sensitivity or network isolation. It can serve to build real-time data warehouses, enable real-time data exchange, data migration, and more.

This article provides release notes for TapData Enterprise, including new features, improvements, and bug fixes.

4.0.0​

New Features​

  • Introduced Tapdata MCP (Model Context Protocol), enabling integration of multi-source data into real-time contextual views consumable by LLMs and AI Agents. This feature is ideal for scenarios with high demands on data freshness and compliance, such as financial risk control.
  • Added support for using StarRocks as a target database, allowing faster construction of real-time data warehouses for high-concurrency, multi-dimensional analytics use cases.
  • Added the ability to choose from multiple data structures when syncing to Kafka, enhancing compatibility and integration efficiency with downstream systems.

Enhancements​

  • When update or delete operations fail to match records on the target side, the system now logs warning messages to aid troubleshooting.
  • Data replication tasks now support filtering tables by primary keys and unique indexes, including: primary key only, unique index only, with either, or without primary key (optionally including unique index).
  • In MySQL-to-MySQL sync scenarios, you can now create indexes based on the first N characters of a text-type field.

Bug Fixes​

  • Fixed an issue where field and table processing nodes displayed incorrectly across pagination in replication tasks.
  • Fixed an ArrayIndexOutOfBoundsException that could occur during incremental sync from Oracle to Doris.
  • Fixed an error that occurred when using a date field as a join key for data validation during sync between Oracle databases.