Skip to content

Release 4.3.2
Compare
Choose a tag to compare
@tonghan-gsh tonghan-gsh released this 28 Sep 05:34
· 384 commits to main since this release
v4.3.2
ee503ea
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

This release focuses on enhancing three key areas:

  • Logical Database Support: Introduced a new logical database feature, providing a fast, reliable, and user-friendly foundation for managing database and table partitions. This update includes logical database configuration, access control management, and the ability to extract logical tables, create new ones, and perform DDL changes.
  • Expanded Data Archiving: Two new archiving paths have been added. Building on the previous version’s support for MySQL to OBMySQL archiving, this update introduces support for Oracle to OBOracle and PostgreSQL to OBMySQL archiving.
  • SQL Development and Data Source Management Enhancements: Usability improvements have been made to the SQL development page, data sources, and forms, with over ten features optimized, including the navigation keys, resource tree objects, and SQL execution results.

For more details on this update, please refer to the version change list.

Feature Updates

  • Logical Database
    • Added support for configuring and removing logical databases.
    • Automatically extract logical tables based on the topology distribution of physical tables to improve efficiency.
    • Provided a new feature for creating logical tables, where users can follow prompts to configure and create logical tables.
    • Added support for submitting logical database DDL change requests through the database change order feature.
    • Added structural consistency checks for logical tables to detect physical table inconsistencies.
    • Logical databases are now included in the existing database and table permission management system, ensuring secure access to logical database data.
  • Data Archiving
    • Added new support for archiving from Oracle to OceanBase Oracle.
    • Added new support for archiving from Oracle to Oracle.
    • Added new support for archiving from OceanBase Oracle to Oracle.
    • Added new support for archiving from PostgreSQL to OceanBase MySQL.
  • Data Cleanup
    • Added support for data cleanup for Oracle databases.
    • Added support for data cleanup for PostgreSQL databases.
  • SQL Checks
    • Added a new SQL row impact check specification for OceanBase MySQL and MySQL data sources, enabling the limitation of large SQL changes to ensure business stability.
  • Partitioning Plan
    • For date-type field partitions, added an option to ensure partition names and partition content ranges are consistent.
  • Data Import
    • The ODC desktop version now supports direct folder selection for data imports.
  • SQL Window
    • Added a feature where clicking the product logo on the SQL development page returns users to the project list page, providing a quick way to return to the homepage.
    • Improved the interaction of the SQL window positioning key, ensuring that the targeted database is automatically displayed in the visible area.
    • SQL executed in the SQL window now shows DB execution time directly on the result tab.
    • Optimized sorting of resource tree objects; resource tree items (data sources, projects, databases, tables, views, etc.) are now sorted by name by default.
    • Users can now initiate all types of tickets directly from databases in the SQL window resource tree.
  • Data Source
    • Databases under a data source can now be filtered quickly based on availability and whether they are assigned to a project.
    • Improved interaction for data source connection initialization scripts, providing quick guides for common parameter configurations.
  • Usability
    • Optimized empty data state interactions across all features (data sources, projects, scripts, resource tree, etc.).
    • Optimized data source selection interactions across all features (database maintenance, sensitive column scanning, adding new databases to projects).
    • For commonly used forms (ticket lists, database lists, user lists), columns that do not display fully (ticket description, data source column, sorting rules, user roles, etc.) now display full content on hover.
    • Added a GitHub issue link on the feedback page, allowing users to provide product feedback quickly via the open-source community.
  • Others
    • SSO integration now supports Azure AD.
    • Updated the platform's login password policy. The latest policy requires a password length of 8-32 characters, containing at least three of the following four character types: numbers (0-9), uppercase letters (A-Z), lowercase letters (a-z), and special characters (all English special characters).

Bug Fixes

  • Data Objects
    • Fixed an error where SQL generated from formatted columns with large data types failed upon execution.
    • Incorrect precision for tinyint type in MySQL mode has been fixed.
    • Resolved an issue where NULL values in CLOB or BLOB columns could not be edited via the GUI.
  • Change Management
    • Fixed incorrect precision for tinyint column types (MySQL data source) in SQL generated by schema comparison tasks.
    • Resolved an issue where partition names were misidentified as table names, leading to permission errors.
    • Fixed a bug where new_table in rename table old_table to new_table was mistakenly flagged as needing new_table permissions.
    • Addressed potential failures in data simulation tasks for MySQL 5.7.
    • Resolved an issue where the manual execution button remained clickable after triggering manual execution.
    • Fixed failure in creating or updating rules when there were too many risk identification rules.
    • Fixed an issue where the page could not scroll when there were too many risk identification rules.
    • Resolved an issue allowing scheduling intervals of less than ten minutes for periodic tasks.
  • Import and Export
    • Fixed an issue where merging PL and table DDL into a single SQL file could cause import failures due to syntax errors.
    • Resolved a bug where path issues could cause export failures on the Windows desktop version.
    • Fixed an issue in OceanBase Oracle mode where exported result sets would be empty if table names were lowercase.
    • Resolved export failures for native MySQL data on the Windows desktop version.
    • Fixed errors when exporting tables with BigDecimal types.
    • Addressed an issue where the result set export would fail when using * and nvl functions in SQL.
    • Fixed export failures for result sets containing SDO-GEOMETRY data types.
  • Data Archiving
    • Fixed errors that occurred when modifying data archiving rate limiting parameters.
    • Corrected inaccurate scan record counts in the details of executed archiving tasks.
    • Fixed a bug in OceanBase Oracle mode where archiving operations would fail if users did not have DBA permissions.
  • Data Source
    • Fixed an issue where testing an OceanBase SYS tenant data source incorrectly succeeded when OceanBase Oracle type was selected.
  • Others
    • Resolved potential SSO login failures in environments with load balancing services.
    • Fixed the issue where the startup parameter ODC_APP_EXTRA_ARGS was ineffective.
Assets 8
Loading