ODC V4.4.3

Version description

ODC 4.4.3 focuses on optimizing the SQL development experience, enhancing platform stability, and improving the permission and security system, comprehensively improving development efficiency and platform reliability.

• SQL development experience optimization: Added a focused mode for the SQL console, which supports inline display of database objects from the resource tree within the SQL window, helping developers focus on in-database development.
• Permission and security management: Added a user project permission dashboard, supporting viewing and editing a user's associated project permissions from their details page.
• Platform stability upgrade: Optimized the underlying metadata synchronization mechanism to reduce the impact on business databases while ensuring timeliness; comprehensively upgraded the bastion host integration solution to improve the stability and usability of integration scenarios.

For more information on the version, please refer to the feature updates.

Considerations

• Upgrade instructions
  • Ensure your ODC version is already V4.3.0 or later; otherwise, upgrade to V4.3.0-V4.4.0 first.
  • Upgrading from V4.3.x to V4.4.3 involves migration and changes to historical data. Please back up the metadata database data before upgrading.
• Upgrade window
  • This upgrade involves migrating historical data for scheduled tasks. If your historical data volume is large, the time required will also increase accordingly. Currently, migrating one million tickets is known to take 20 minutes. Arrange the upgrade during an appropriate business idle period.
  • To minimize upgrade time, refer to Preparations for upgrade to migrate historical data first, then proceed with the upgrade.
• Tickets
  • If there are unfinished (pending approval, pending execution, in progress) tickets before the upgrade, they may be terminated or fail.
• Scheduled tasks
  • In this upgrade, four types of tickets: data archiving, data cleanup, SQL plan, and partitioning plan, are migrated to the job module.
  • For all scheduled tasks, if there are unfinished approval workflows during the upgrade, they may be terminated after the upgrade.
  • If open windows for data archiving, data cleanup, partitioning plans, or SQL plans existed in the SQL console before the upgrade, an error message may appear after the upgrade. Reopening the corresponding window will no longer trigger the error.
  • Regarding partitioning plans:
    • After migration, the new job number will not match the original ticket number.
    • Partitioning plans that failed approval (pending approval, approval expired, approval failed) will not be displayed in the job list.
    • Partitioning plans with an empty partitioning strategy will not be displayed in the job list.
  • Regarding execution records:
    • After migration, the historical execution record numbers in the new job will not match the original execution records.
    • If there are unfinished execution records for partitioning plans or SQL plans, the execution record status may be inconsistent with the actual situation after the upgrade. You can run scripts after the upgrade to correct the data. For detailed operations, see the Correct data section in Upgrade verification.
    • 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 scripts after the upgrade to hide the data. For detailed operations, see the Hide data section in Upgrade verification.
• Logical database changes
  • Historical data of logical database change tickets will not be supported after the upgrade. You can run scripts to obtain historical change data from the metadata database. For detailed operations, see the Check historical logical database change data section in Upgrade verification.

ODC V4.4.3

• Current version: V4.4.3

• Previous version: V4.4.2

• Release date: June 3, 2026

• Supported upgrade path: You must first upgrade ODC V2.0.0 and later versions to V4.3.0–V4.4.0 before you can upgrade to this version.

Feature updates

• SQL console

  • Added focus mode, which displays objects within a database in the resource tree in the SQL window, helping users focus on development within the database.
  • Optimized global search content by removing column search to improve metadata synchronization efficiency.

• User permissions

  • Added a project permission dashboard in user details, facilitating unified management of all project roles for a user.
  • The project permission dashboard supports viewing all project permissions of a user.
  • The project permission dashboard supports exporting a user's project data to a CSV file.
  • The project permission dashboard supports adding a user to a new project, modifying a user's existing project role, and removing a user from existing projects.

• SQL editor

  • Supports nested query SQL completion, optimizing alias suggestion and multi-level nested suggestion.

• Data cleanup

  • Supports quick batch selection of partitions using regular expressions, facilitating quick filtering of target partitions.

• Import

  • Added an entry for configuring to ignore foreign key checks, allowing users to skip foreign key constraint import.

• Data source

  • Supports batch export of data source information. To ensure data security, the key content in the exported file is encrypted.
  • Supports re-importing exported content into the data source module, improving data source migration efficiency.

• seekDB

  • Supports the seekDB data source type, enabling daily data development on SeekDB.

• OBServer adaptation

  • Supports the Array field type. The GUI allows creating, viewing, and managing tables containing Array fields.
  • Bit type fields display a specified length of content based on the field definition.

• Bastion host integration

  • For bastion host integrated login scenarios, only the currently logged-in data source is displayed, avoiding interference from redundant information.

• Metadata synchronization

  • Upgraded the synchronization scheme, optimized the synchronization timing, and no longer synchronizes field (column) information.

• Temporary data sources

  • Added a heartbeat detection mechanism. Temporary data sources are automatically cleared if there is no heartbeat within a specified time period, preventing the accumulation of redundant temporary data sources.
  • Optimized the metadata synchronization strategy for temporary data sources. They no longer participate in daily scheduled synchronization or every 4-hour synchronization, avoiding interference with the business database.