ODC V4.5.0

Considerations

• Upgrade instructions

  • Make sure that your ODC version is 4.3.0 or later. If not, first upgrade it to 4.3.0–4.4.0.

  • Upgrading from 4.3.x to 4.5.0 involves migrating and modifying historical data. Therefore, back up the metadata database before you upgrade.

• Upgrade window

  • This upgrade involves migrating historical data of scheduled tasks. If your historical data volume is large, the migration time will also be longer. We know that migrating one million tickets takes about 20 minutes. Arrange the upgrade during an idle business period as appropriate.

  • To minimize the upgrade time, follow the documentation to migrate the historical data first and then perform the upgrade.

• Ticket tasks

  • If there are unfinished (pending approval, pending execution, or in progress) tickets before the upgrade, they may be terminated or fail to execute.

• Scheduled tasks

  • In this upgrade, four types of tickets—Data Archiving, Data Cleanup, SQL Plan, and Partitioning Plan—are migrated to the Jobs module.

  • For all scheduled tasks, if there is an unfinished approval flow during the upgrade, the approval flow may be terminated after the upgrade.

  • If any windows for Data Archiving, Data Cleanup, Partitioning Plan, or SQL Plan were open in the SQL console before the upgrade, an error message may appear when you reopen the corresponding window after the upgrade. However, the error will no longer occur upon reopening.

  • Partitioning Plan:

    • After the partitioning plan is migrated, the new job number will be different from the original ticket number.
    • Partitioning plans that have failed to pass approval (Pending Approval, Approval Expired, or Approval Failed) for creation will not be displayed in the job list.
    • Partitioning plans with an empty partitioning strategy will not be displayed in the job list.

  • Execution record:

    • After the partitioning plan or SQL plan is migrated, the numbers of historical execution records in the new job will be different from the original execution records.
    • If there are unfinished execution records for a partitioning plan or SQL plan, the execution record status may be inconsistent with the actual situation after the upgrade. You can run a script after the upgrade to correct the data.
    • Historical execution records for partitioning plans and SQL plans will still be displayed in the Database Change List. If you do not want them to be displayed, you can run a script after the upgrade to hide the data.

• Logical database changes

  • After the upgrade, you cannot view historical data of change tickets for logical databases. You can run scripts to obtain historical change data from the meta database.

ODC V4.5.0

• Current version: V4.5.0

• Previous version: V4.4.0

• Release date: July 31, 2026

• Supported upgrade path: You can directly upgrade from ODC V4.3.0 and later versions to this version.

Feature updates

• Login integration

  • Fixed an issue where the approval flow integration failed under specific conditions.

  • Fixed an issue where the employee ID was not automatically padded with zeros when the length was insufficient in the login integration of Apsara Stack.

• MCP

  • Provided the MCP interface to support external system docking and automated integration.

• SQL console

  • Fixed the issue where max_active was hardcoded as 5 in the code. It has been changed to a configurable parameter to improve the flexibility of concurrent connection management and adaptability to different environments.

  • The SQL window auto-completion now supports more object types.

  • Removed the row limit of 100,000 rows for exported data in the SQL console.

• OpenAPI

  • Some ODC features are now provided through OpenAPI.

• Jobs

  • Optimized the CPU check for excessive SQL resource usage and its high frequency.

• Tickets

  • Adjusted the text for execution details of logical database changes to "execution records".

  • Enabled ticket import and export interoperability between the Apsara Stack version and the cloud version.

• Partitioning plans

  • Added a risk warning that deleting a partition in a partitioned table containing a GLOBAL INDEX may block new partition creation.

• System language

  • Added support for Japanese.

• Message notification

  • Added configuration items to pause and resume message notifications, allowing users to configure silent notification delivery during specific periods.

• Join a project

  • When applying to join a project, you can now search for clusters or tenants to join the corresponding project.

Bug fixes

• Fixed an issue where ODC would fail when executing DDL statements for creating PKGs that contained /* */ comments following a BEGIN, including selecting and executing the final terminator /.
• Fixed an issue where, after taking one node offline during multi-node ODC deployment, tasks assigned afterward would remain in the Scheduling state indefinitely.
• Fixed an issue where database administrators could not participate in task approval when deleting or terminating a task.
• Fixed an issue where only 10 templates were displayed for multi-database changes.
• Fixed an issue where issuing a multi-database change task for more than 60 databases would fail.
• Fixed an issue where selective data column import would fail when importing a CSV file.
• Fixed an issue where the desktop version supported importing TXT files.
• Fixed an issue where using regular expressions for data mocking could cause a DFA state explosion, leading to an OOM error.

Dependency component versions