Skip to main content

What's New

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

4.9.0​

New Features​

Enhancements​

  • While creating APIs, parameters now support the IN operator (e.g., caseType IN ('I', 'A')). Custom queries now support required/optional parameter settings and field filtering.
  • Optimized QPS metrics display on the task monitoring page, now including CPU and memory usage trend charts.
  • UI enhancements across the platform for a better user experience.

Bug Fixes​

  • Fixed an issue where setting group tags in user management could incorrectly set the user status to “Reject.”
  • Fixed a problem in multi-node deployments where license updates on the frontend were not propagated to all nodes.

4.8.0​

New Features​

Enhancements​

  • Enabled rolling upgrades for the API service to ensure uninterrupted availability during updates.

Bug Fixes​

  • Fixed an issue where the audit log could not identify client information when the token had expired.
  • Fixed an issue where the Limit parameter in API requests was not being applied correctly.

4.7.0​

New Features​

  • Added support for configuring field masking rules when creating APIs. Masked fields will also appear masked in audit logs and debug results, improving data security.
  • When publishing custom query APIs, users can now preview and edit the final query statement and use custom parameter values.
  • API responses now support returning only specific fields from nested documents or arrays, reducing data redundancy and improving performance.

Enhancements​

  • Added the ability to configure API database timeout settings in the system settings. When a request times out, clear log messages are generated to simplify troubleshooting.
  • Improved the generated API Swagger documentation to fully include request bodies, response formats, and error codes, enhancing integration efficiency and consistency.

4.6.0​

New Features​

  • Added support for defining business aliases for fields when creating APIs, improving semantic readability and standardization of field names.
  • When publishing a Custom Query API, you can now preview and edit the generated SQL statement, and reference user-defined parameters—offering a more flexible API configuration experience.

Enhancements​

  • Added an “Ignore Update Events” option for child table merge logic, reducing redundant triggers and minimizing unnecessary data updates.
  • Support for customizing license alert levels and email templates, helping enterprises meet compliance and notification requirements.
  • Added a Set API Access option on the role management page, enabling quick assignment of API access permissions to roles, improving authorization efficiency.

Bug Fixes​

  • Fixed an issue where the maximum number of rows returned by an API did not take effect in system settings.
  • Fixed a display error in the API audit page.

4.5.0​

Enhancements​

  • Improved write performance when using Feishu Bitable as a target database.
  • Optimized the source and target configuration interfaces to make interactions clearer, improving usability and configuration efficiency.

Bug Fixes​

  • Fixed an issue where specified return fields for APIs were not applied correctly.

4.4.0​

New Features​

  • Incremental data validation now supports tables without primary keys, along with manual repair. This expands validation coverage and helps ensure data consistency.
  • Added alert notifications during task retries to improve visibility and responsiveness in failure scenarios.
  • Introduced "Node Data Preview" in the task editor, allowing you to view sample fields instantly while configuring tasks—speeding up design and troubleshooting.

Enhancements​

  • Improved data source monitoring: Added connection status and performance metrics for Sybase and PostgreSQL, enhancing system observability.

4.3.0​

New Features​

  • Data validation now supports exporting repair SQL for inconsistent results, with compatibility for PostgreSQL, Sybase, and SQL Server. This makes offline auditing and rollback easier for ops teams.
  • JS Processor Node now supports the unset operation, enabling targeted field removal in MongoDB. Ideal for cleanup and payload optimization.

Enhancements​

  • Refined logic for marking full sync tasks as completed: now based on whether all writes to the target are finished—more aligned with real business completion.

4.2.0​

New Features​

Enhancements​

  • Optimized index synchronization logic to preserve index names in the target database, improving consistency and business traceability.

Bug Fixes​

  • Fixed an issue where searching shared mining tasks by connection name caused a page error.

4.1.0​

New Features​

  • Added support for Incremental Data Validation within tasks. This feature continuously verifies target-side data consistency during synchronization, improving validation efficiency and enhancing overall data reliability.

Enhancements​

  • Improved the user experience of the data validation interface to make the process more intuitive and feedback more informative.

Bug Fixes​

  • Fixed an issue where an unclear error message was shown when creating an Oracle data source with a non-existent account. The system now explicitly indicates that the account does not exist.

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(e.g. Flink) when syncing to Kafka-Enhanced, 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.