RELEASE NOTE

About this version

This version fixed some bugs.

BUGFIX

• Fix observer restart failed in some extreme environment because fetch slog again failed.（ #a09d313）；
• Decrease the memory limit of MINI MODE docker image.（ #7a49bef）；

发布说明

发版目的

本次发版主要是BUG修复。

BUG 修复

• 修复极端场景下，ob重启回放slog失败，导致启动失败的问题（ #a09d313）；
• 调低MINI MODE的内存限制（ #7a49bef）；

RELEASE NOTE

Please refert to https://open.oceanbase.com/blog/10900260 for more Details.

| Item | Description | | -------- | ------------------ | | Release date | 2022-3-30 | | Release number | V3.1.3 | | Commit number | 3d79cacb37012cf61b7cb8faf00d9a6bb152bcd1 |

About this version

In V3.1.3, OceanBase Database enhanced its ecological capabilities to provide better services for community users.

• Supports JSON data types and provides OBKV HBASE client, to support semi-structured and NoSQL scenarios.
• Supports connecting to OceanBase Database via MySQL native drivers including Python, Go and ODBC, supports k8s container orchestration by using ob-operator, and supports ARM platforms.
• Stranger product capabilities: supports a minimum resource specification of 2C8GB, and improves the reliability of CDC link synchronization.

New features

Support JSON data type

In this version, OceanBase Database supports DDL, index creation, SQL query and data type conversion operations, and supports all the JSON functions of MySQL 5.7 and some of JSON functions of MySQL 8.0.

• Supports four basic types (string, number, bool and NULL) and two structural types (objects and array).
• Supports creating a JSON type column when creating a table or add a column.
• Supports creating indexes on the basis of a JSON type column.
• Supports referencing JSON objects using -> and ->> operators.
• Supports using JSON text in SQL statements, including SELECT/INSERT/UPDATE/DELETE.
• Supports all the JSON functions of MySQL 5.7 and some new JSON functions (for example, JSON_OVERLAPS() and JSON_VALUE() ) of MySQL 8.0.

Provide OBKV HBASE client

Applications can obtain API interfaces that are compatible with HBASE (HBASE 0.94) by using this client, and communicate with OceanBase Database via TABLE API interface protocol. Besides, in this version, OceanBase Database supports WideColumn data mode, optimizes the Filter logic, and supports KEY, RANGE and Prefix partitions.

Compatible with MySQL native drivers

In this version, OceanBase Database supports being connected via the following MySQL native drivers:

• Supports Python3 pyMySQL and Python2 MySQL-python drivers.
• Supports golang Go-SQL-Driver/MySQL driver.
• Supports Unix ODBC driver.

Provide ob-operator and support K8s container orchestration

With ob-operator, OceanBase Database can be deployed on Kubernetes clusters on public cloud or on-premise environments. ob-operator can be deployed by using YAML files or Kustomize. ob-operator provides the following functions.

• Supports deploying OceanBase clusters on k8s.
• Supports creating, deleting , scaling in/out clusters and lifecycle management of clusters.
• Supports creating and deleting Zone.
• Supports creating, deleting, restarting OBServer instances.
• Supports viewing cluster, Zone and OBServer status via kubectl commands.
• Supports managing k8s resources via HTTP API.

Support ARM platforms

OceanBase Database and OBProxy are tested and verified on ARM platforms. In V3.1.3, users can develop, compile and test and deploy applications on ARM platforms.

Support lower specifications

In V3.1.3, OceanBase Database provides 2C8GB Docker images. Users can learn and use OceanBase Database with less resources. Enhance the reliability of CDC data synchronization Formerly, the data captured by CDC from OceanBase Database is stored in memory and then provided to downstream consumers, and this presents very high requirements on server specifications and might cause data synchronization failure on customers' key business. Therefore, OceanBase Database enhances the sychronization capability of CDC link.

• Supports persistence mode. Before data sychronization, data is first stored temporarilly in local disk and then be transferred to the downstream consumers via the CDC link, and the transaction data stored in local disk is deleted after being consumed, thus reducing the capacity of memory occpied during data synchronization.
• Supports big transaction. In V3.1.3, OceanBase Database optimizes the usage of memory during big transaction synchromization. This together with the persistence mode can fultill the data synchronization requirements in big transaction scenarios.

Improves usability

• Resource capacity parameters (storage and memory) can be configured as a decimal, for example, alter system set datafile_size ='11.5G';.
• Links directing to the related help information is printed when errors occur to OBD.
• ob_admin will filter out business data while performing Clog parsing.
• information_schema.TABLES supports ENGINE.
• Documentations are opened to github where you can commit doc issues and push requests.

Feature changes

• Change the default index of partition table to local index To better meet business requirements, the default index created on partition table is changed to local index. If you want to create global index, refer to create table ad1(c1 int primary key, c2 int, index(c2) global)partition by key(c1) partitions 2;.
• Change to default table creation action to non-strict mode By default, OceanBase Database judges that a table is successfully created when the majority of replicas are successfully created. If you want to use the strict mode, set ob_create_table_strict_mode to False.

Bugfixes

• Fixes the flashback table function. Tables deleted will be stored temporarilly in the recycle bin of OceanBase Database, and can be restored using the flashback table command.
• Fixes the defect that when the TIMESTAMP precision is modified the time value returned changes. In V3.1.3, when the TIMESTAMP precision is modified, for example modifying the column type from TIMESTAMP(0) to TIMESTAMP(6), the time value returned will not change.
• Error message will be returned when using the ALTER SYSTEM SET DATAFILE_SIZE command to set the data file size to a smaller value.
• Fixes the defect that incremental backup will fail when the transaction status table is not null.

版本信息

更全版本信息, 请参考https://open.oceanbase.com/blog/10900260 .

| 名称 | 描述 | | -------- | ------------------ | | 发布时间 | 2022-3-30 | | 版本号 | V3.1.3 | | 提交号 | 3d79cacb37012cf61b7cb8faf00d9a6bb152bcd1 |

概要说明

在 V3.1.3 版本，OceanBase数据库进一步增强社区生态能力，更好地服务广大社区用户。

• 多模应用：新增JSON格式数据类型和OBKV HBASE 客户端，支持半结构化和NoSQL类型业务场景应用。
• 生态能力增强：支持MySQL原生的Python/Go/ODBC类型驱动连接OceanBase数据库，发布ob-operator支持K8s容器编排，支持ARM平台编译运行。
• 更优的产品能力：支持更小的资源规格（2C8GB），提升CDC链路同步可靠性。

特性更新

支持 JSON 格式数据类型 支持 DDL、索引创建、SQL 查询、数据类型转换等基本操作，兼容MySQL 5.7 版本的全量以及 8.0 版本的部分 JSON 函数。

• 支持四种基本类型（字符串、数字、布尔值和 NULL）和两种结构化类型（对象和数组）。
• 支持在创建表、添加列时创建类型为 JSON 的列。
• 支持基于 JSON 列的生成列创建索引。
• 支持通过 ->、->> 操作符引用 JSON 对象。
• 支持在 SELECT/INSERT/UPDATE/DELETE 等 SQL 语句中使用 JSON 文本。
• 支持MySQL 5.7 版本的全量 JSON 函数以及 JSON_OVERLAPS()、JSON_VALUE() 等 8.0 版本新增函数。

开源 OBKV HBASE 客户端

应用可以通过该客户端获得HBASE语法兼容（HBASE 0.94版本）的API接口，与OceanBase数据库通过TABLE API 接口协议进行通信。在数据模型上增加宽表模型（WideColumn），优化 Filter 逻辑，支持 KEY 分区、RANGE 分区和前缀分区。

兼容MySQL原生驱动

支持更多MySQL生态原生驱动连接OceanBase数据库：

• 新增支持Python3 pyMySQL和Python2 MySQL-python驱动。
• 新增支持golang Go-SQL-Driver/MySQL驱动。
• 新增支持Unix ODBC驱动。

发布ob-operator，支持K8s容器编排

通过使用 ob-operator，OceanBase 数据库可以以容器的形式运行在公有云或私有化部署的 Kubernetes 集群上。用户通过 YAML或Kustomize 部署 ob-operator，ob-operator 以服务的形式提供如下能力：

• 在 K8s 环境下独立部署 OceanBase 集群。
• 支持集群的创建、删除、扩容、缩容和生命周期管理。
• 支持Zone的创建、删除。
• 支持OBServer实例的创建、删除、重启、故障转移。
• 支持使用 kubectl 命令查看集群、Zone和OBServer 的状态。
• 支持通过 HTTP API 管理 K8s 资源。

新增支持 ARM 平台

完成OceanBase 数据库与OBProxy中间件在ARM架构平台下的适配验证，并发布基于ARM架构的版本，社区用户可以在ARM平台下进行业务开发、编译测试和应用部署。

支持更小规格

发布2C8GB资源规格的Docker镜像，方便社区开发者使用更小的资源学习和使用OceanBase数据库，降低入门成本。

CDC数据同步可靠性增强

CDC 从 OceanBase 数据库拉取的数据以内存态的形式提供给下游消费者，对机器资源配置规格有较高要求，对于用户的关键业务场景（例如大数据量入库场景），可能会造成数据同步失败。因此，我们对CDC链路的数据同步能力进行增强：

• 支持持久化模式，数据在同步开始前先进行本地临时存储，然后再通过CDC链路同步给下游消费者，待消费完毕后清理本地临时存储的事务数据，减少数据同步过程中对内存的占用。
• 支持大事务，优化大事务同步时对内存的使用，结合持久化模式，满足大事务场景下的数据同步需求。

产品易用性增强

• 资源容量（存储、内存）相关配置项支持小数设置，例如：alter system set datafile_size ='11.5G'。
• OBD 在报错时提供帮助链接地址。
• ob_admin支持在Clog解析时过滤用户数据。
• information_schema.TABLES 增加 ENGINE 值。
• 文档开源，支持通过github提交文档issue和pr。文档包括架构设计原理、性能调优、故障处理、日常维护指导等。

行为变更

• 分区表默认创建的索引变更为本地索引 在一些客户使用过程中我们发现 ，需要经常对分区表的索引性能进行调优，经过分析总结，发现局部索引更适合多数客户业务场景，因此我们将分区表默认创建的索引调整为本地索引。如果需要创建全局索引，可以参考示例 create table ad1(c1 int primary key, c2 int, index(c2) global)partition by key(c1) partitions 2。
• 修改创建表的默认行为为非严格模式 OceanBase 数据库建表时只要求多数派副本创建成功即认为建表成功。如果需要使用严格模式创建表，需要将系统变量ob_create_table_strict_mode设置为True。

问题修复：

• FLASHBACK TABLE 功能修复，删除的表会临时存放在数据库的回收站中，用户可以通过 FLASHBACK TABLE命令恢复表和数据。
• 修复TIMESTAMP值域变更导致的显示错误问题，例如：列类型由TIMESTAMP(0)修改为TIMESTAMP(6)，保证前后查询时间结果显示一致。
• 修复ALTER SYSTEM SET DATAFILE_SIZE命令执行报错，若将数据文件大小变更缩小直接报错返回。
• 修复因事务状态表非空导致增量备份失败的缺陷。

RELEASE NOTE

Version information

| Item | Description | | -------- | ------------------ | | Release date | 2021-12-30 | | Release number | V3.1.2 | | Commit number | d4ace121deae5b81d8f0b40afbc4c02705b7fc1d |

About this version

In V3.1.2, we provided free GUI developer tool (ODC), maintenance and monitoring tool (OCP), data migration tool (OMS), OBDUMPER, and OBLOADER for OceanBase users. OceanBase supported online cross-version upgrade. You can specify the target upgrade version by using OBD. OBD will automatically find the best upgrade solution and do the upgrade for you. The upgrade process does not affect your business. We optimized the update of hot row data and improved the performance by 300%. We optimized the delimination mechanism of SQL PLAN for partition tables. We optimized the underlying communication code. We added multiple SQL MODE functions and system functions.

New features

• Developer center (ODC): OceanBase Developer Center Community Version is a development platform for OceanBase database. ODC supports database objects visual management, intelligent syntax, session management, recycle bin management, data import or export, and resource and permission management. Key features of ODC are:

  • Multi-window development mode: Provided SQL window, anonymous block window, and command line window development modes. You can choose your development mode based on your habits. The SQL window and anonymous block window supports advanced features such as intelligent auto-completion, syntax highlighting, and formatting, etc.
  • Rich result set management: Supported the interactive operation of result set tabulation. Supported exporting all or part of the query result set in SQL window.
  • Flexible import and export: Supported SQL, CSV, and other format data files. You can import or export a single table, multi-table, or all data in a database at one time. Supported importing or exporting the defined objects and tables separately or together.
  • Collaboration management: Supported built-in control platform. You can edit the roles and permissions for user groups, and manage connection resources to improve your collaboration efficiency.

• Maintenance and monitoring tool (OCP): OceanBase Cloud Platform (OCP) is a cluster management tool for OceanBase Database. With OCP, you can manage and operate your hosts, networks, software packages, and the full lifecycle for your clusters and tenants. With OCP, you can also decrease your IT O&M cost. Key features of OCP are:

  • Cluster management: Supported cluster installation, operation, and maintenance, performance monitoring, configuration, upgrade, deletion, adding or removing hosts.
  • Tenant management: Supported creating tenant, tenant topology, performance monitoring, session management, and parameter management.
  • Monitoring and alerts: Supported monitoring clusters, tenants, and hosts. You can use the built-in alerts or customize your alerts. You can use templates to configure HTTP or customize script channels for various message channels.
  • System management: Supported viewing tasks and managing running tasks. You can customize parameters based on your business.
  • Security: Supported creating, altering, and deleting database users and roles, granting and revoking permissions for roles. You can manage OCP users' settings, passwords, and alarm subscriptions through User Center.

• OceanBase Migration Service (OMS): You can use the OceanBase Data Migration Tool (OMS) Community Edition to migrate data from heterogeneous databases to OceanBase databases. OMS supports online data migration and real-time synchronization of incremental data. All changes to OceanBase database are synchronized in real-time to the source database before migration. You can use the management console to create data migration projects, customize task configuration and monitor the OMS transfer components. Key features of OMS are:

  • Database objects migration: Supported exporting, switching, and creating tables, indexes, constraints.
  • Full data migration.
  • Incremental data migration: Supported real-time incremental data synchronization from the source database to the target database through log parsing.
  • Full data verification: Supported full data verification between source data and target data. Provided scripts to correct the inconsistent data.
  • Reverse incremental migration: When the business switches the application to the (source) target data, the incremental data in the target database is synchronized back to the source database in real-time.
  • Supported MySQL versions: 5.6, 5.7.
  • Supported customized alarm settings.
  • O&M monitoring: Supported monitoring on hosts and components.

• OBLOADER/OBDUMPER: You can use OBLOADER or OBDUMPER to import or export data. To improve concurrent performance for OBLOADER or OBDUMPER, you can specify the concurrency number, the paging query records number, and the batch number based on your kernel load capacity. OBLOADER and OBDUMPE support exporting SQL by partition, specified conditions, single table, multi-table, full database, and customized queries. OBLOADER and OBDUMPE support data pre-processing, field mapping import. OBLOADER and OBDUMPE are compatible with SQL, CSV, CUT, etc.

• Supported online rotating upgrade across versions: You can upgrade your OceanBase database with the obd cluster upgrade command. OBD automatically identifies the upgrade path between matching versions and does a rotating upgrade for each Zone. For more information, see OBD document.

• Optimized data hotspot row: To update hotspot data, OceanBase used lock for write and released row-level locks before filling logs. This increased the concurrent update performance from 3000TPS to 9000TPS and expanded the upper limit for hotspot data processing.

• Optimized the elimination mechanism for partition table SQL PLAN: In distributed scenario plan evaluation, there is no accurate feedback on the number of rows in the remote node partition. And there is a risk of plan degradation. OceanBase uses the final SQL execution time feedback to negatively optimize the execution plan. When the average execution time of the sampled query exceeds twice the first execution time, the PLAN is targeted to be eliminated and a new SQL PLAN is generated to solve the bad performance caused by the degradation of the SQL PLAN.

• Optimized the communication clock stability: OceanBase uses CPU clock (SYS_clock_gettime) to get the timeout time for its underlying communication framework. However, the upper SQL layer uses OS clock (get_timeofday) to record the timeout time. The difference between these two times may cause the upper business layer to reset the original error code for the bottom layer. With the timeout difference tolerance design, OceanBase reproduces the system error and improves the error locating efficiency.

• Compatibility with MySQL: Supported some new system functions:

  • VALIDATE_PASSWORD_STRENGTH(): This function returns an integer to indicate how strong the password is. The return value ranges from 0 (weak) to 100 (strong). For example, SELECT VALIDATE_PASSWORD_STRENGTH('[email protected]');。
  • UUID_SHORT(): Returns a “short” universal identifier as a 64-bit unsigned integer. For example, SELECTUUID_SHORT();。
  • TO_BASE64() and FROM_BASE64(): TO_BASE64() returns the argument converted to a base-64 string. For example, SELECT TO_BASE64('12345'). FROM_BASE64() decodes base64 encoded string and return result. For example, SELECT FROM_BASE64('MTIZNDU=');.
  • DAY(): Returns the day of the month (0-31). For example, SELECT DAY('2021-12-12');.
  • ANY_VALUE(): Suppress ONLY_FULL_GROUP_BY value rejection.

• Open sourced OBKV TABLE JAVA Client: Provided direct access to the underlying OceanBase database stored table data through the TABLE API interface protocol. You can call this API as a JAR package in development. TABLE API supports authentication, add, delete, check, and append operations. For more information, see GitHub repo

• Open sourced OBKV HBASE API: Based on the basic interface protocol provided by the TABLE API, we added the wide table model (WideColumn) for the data model, optimized the filter logic, supported KEY partitioning, RANGE partitioning, prefix partitioning, and TTL. Compatibility with HBase API client is coming soon.

• Supported UOS platform operating system: OceanBase and obproxy are fully compatible with the mainstream X86 platform operating system. For more information, see OceanBase GitHub repo.

• Enhanced administrator tool ob_admin: supported parsing and explicitly exporting block_file files, archive files, backup meta information, and data. The input command is ob_admin dumpsst/archive_tool/dump_backup. For more information, see ob_admin document.

• Enhanced OceanBase Community Edition documentation. Documentation includes architecture design principles, performance tuning, troubleshooting, daily maintenance guidance,etc.

Bugfixes

• Fixed __all_virtual_memory_info returs incomplete tenant information. This is caused by MEMOEY APPEND.
• Fixed global index creation failure caused by killing observer. OceanBase triggers retry for this scenario to make sure a successful index creation.
• Fixed the error triggered by writing long column values.
• Fixed compiled error on CentOS 8.3 and 7.9 platform. For more information, see Issue 714 and Issue 715.

版本信息

| 名称 | 描述 | | -------- | ------------------ | | 发布时间 | 2021-12-30 | | 版本号 | V3.1.2 | | 提交号 | d4ace121deae5b81d8f0b40afbc4c02705b7fc1d |

概要说明

在 V3.1.2 版本，我们为 OceanBase 用户提供了免费的图形界面开发者工具（ODC）、运维监控云平台（OCP）、数据迁移工具（OMS）、导数工具（OBLOADER 和 OBDUMPER） 。OceanBase 支持在线跨版本轮转升级，通过 OBD 指定需要升级到的版本，自动完成最佳升级路径解析和应用升级，全过程无需人工干预且不影响业务运行。优化了热点行数据更新，性能提升了 300%。优化了分区表 SQL PLAN 淘汰机制。优化了底层通信代码等。新增了多个 SQL MODE 和系统函数。

特性更新

• 开发者中心（ODC）：OceanBase 社区版开发者中心（ODC）是为 OceanBase 数据库量身打造的开发平台。为数据库开发者提供了数据库对象的可视化管理、智能语法、会话管理、回收站管理、导入导出、资源和权限统一管理等多种能力。ODC 核心功能如下：

  • 多窗口开发模式：ODC 提供 SQL 窗口、匿名块窗口和命令行窗口开发模式。您可以按照自身习惯选择打开对应模式窗口进行开发，SQL 窗口与匿名块窗口支持智能联想提示、语法高亮、格式化等高级功能。
  • 丰富的结果集管理：支持对结果集表格化的交互操作，可导出全部和部分的 SQL 窗口内的查询结果集。
  • 灵活的导入导出：支持 SQL、CSV 和其他数据格式的文件，可以一次导入和导出单表、多表或全库数据。支持定义对象和表数据单独或混合导入导出。
  • 协作管理：内置管控平台，您可以编辑用户群体的角色和权限，管理连接资源，提升企业协作管理效率。

• 运维监控工具（OCP）：OceanBase 社区版运维监控工具（OCP）是为 OceanBase 数据库量身打造的企业级数据库集群管理平台工具。您可以使用 OCP 管理和运维主机、网络、软件包等资源，管理集群和租户的全生命周期，降低 IT 运维成本。OCP 的核心功能如下：

  • 集群管理：支持集群的安装、运维、性能监控、配置、升级、删除、主机添加和删除等功能。
  • 租户管理：支持租户的创建、结构拓扑图、性能监控、会话管理和参数管理等。
  • 监控告警：支持集群、租户和主机三种维度的监控告警。您可以使用内置告警项或自定义配置告警项，可以选择 HTTP 通道或者脚本通道传递告警消息。
  • 系统管理：支持查看和管理运行中的任务，根据业务自定义参数配置。
  • 安全 ：支持创建、修改或删除数据库用户和角色，赋予和回收角色的权限。您可以通过用户中心管理 OCP 用户的个人设置、密码和告警订阅等信息。

• 数据迁移工具（OMS）：您可以使用 OceanBase 社区版数据迁移工具（OMS）实现异构数据库与 OceanBase 数据库的数据迁移。OMS 支持将异构数据库在线不停服地迁移至 OceanBase 数据库，同时在应用切换至 OceanBase 数据库后，将 OceanBase 数据库上所有的变更数据实时同步至切换前的源端数据库。您可以使用管理控制台创建数据传输项目、自定义任务配置和监控运维传输组件。OMS 的核心功能如下：

  • 支持数据库对象迁移：包括表、约束、索引的自动导出、转换和创建。
  • 支持全量数据迁移。
  • 支持增量数据迁移：通过日志解析将源端实时的增量数据迁移至目标端。
  • 支持全量数据校验：源端和目标端表数据全字段的数据比对，对不一致的数据提供订正 SQL 语句。
  • 支持切换后反向增量迁移：业务将应用切换至(源)目标端数据源时，将目标端增量数据实时同步回源端。
  • 支持的 MySQL 版本包括：5.6、5.7。
  • 支持用户自定义告警设置。
  • 支持运维监控：包括主机监控、组件监控和组件运维。

• 数据导入导出工具（OBLOADER/OBDUMPER）：您可以使用 OBLOADER 和 OBDUMPER 快速导入和导出数据。您可以根据内核的负载能力指定并发数、分页查询的记录条数及分批处理数来提升导入和导出的并发性能。OBLOADER 和 OBDUMPER 支持按照分区、指定条件、单表、多表、全库、以及自定义查询 SQL 导出，支持数据预处理、字段映射导入，兼容 SQL，CSV、 CUT 等多种文本格式。

• 支持在线跨版本轮转升级：您可以通过 obd cluster upgrade 命令升级 OceanBase 数据库。OBD 自动识别匹配版本间的升级路径，对每个 Zone 进行轮转升级。更多信息，参考 OBD 使用指导。

• 数据热点行优化：在热点数据更新场景中，OceanBase 通过对 lock for write 加锁逻辑、填充日志前释放行级锁优化，使得 OceanBase 在处理热点数据的并发更新性能从 3000TPS 提升到 9000TPS，提升了热点数据处理能力上限。

• 优化了分区表 SQL PLAN 的淘汰机制：在分布式场景计划评估中，无法准确获得远端节点分区的行数反馈，存在计划退化的风险。OceanBase 采用最终 SQL 执行时间反馈负向优化执行计划，当采样的查询平均执行时间超过首次执行时间的 2 倍时，则针对性淘汰该 PLAN 并重新生成新的 SQL PLAN，解决因 SQL PLAN 劣化导致的性能下降问题。

• 通信时钟稳定性优化：OceanBase 底层通信框架使用 CPU 时钟（SYS_clock_gettime）获取超时时间，而上层 SQL 业务逻辑是使用操作系统时钟（get_timeofday）记录超时时间的，这两种时间精度上的误差会有极低概率导致上层业务逻辑重置底层的原始错误码，OceanBase 通过设计可容忍超时误差计算逻辑，准确还原出系统运行报错的第一现场，提升问题分析诊断效率。

• MySQL兼容：新增支持系统函数：

  • VALIDATE_PASSWORD_STRENGTH()：该函数用来给密码的安全性进行评分，返回 0-100。如 SELECT VALIDATE_PASSWORD_STRENGTH('[email protected]');。
  • UUID_SHORT()：该函数可以生成一个 64 位无符号整数。如 SELECTUUID_SHORT();。
  • TO_BASE64() 和 FROM_BASE64()：该函数提供基于 base-64 算法的字符编码与解码能力。如 SELECT TO_BASE64('12345') 和 SELECT FROM_BASE64('MTIZNDU=');。
  • DAY()：该函数返回给定日期的月份的日期部分。如 SELECT DAY('2021-12-12');。
  • ANY_VALUE()：该函数用来抑制 ONLY_FULL_GROUP_BY 的值被拒绝。

• 开源 OBKV TABLE JAVA Client：提供通过 TABLE API 接口协议直接访问 OceanBase 数据库底层存储表数据的操作方式，用户开发程序可以以 JAR 包的形式调用该接口，支持认证、对行增删改查追加等操作。详见GitHub代码仓库(https://github.com/oceanbase/obkv-table-client-java)

• 开源 OBKV HBASE API：基于 TABLE API 提供的基本接口协议，在数据模型上增加宽表模型（WideColumn），优化 filter 逻辑，支持 KEY 分区、RANGE 分区和前缀分区，支持 TTL。兼容 HBase API 客户端持续开源中。

• 新增配置支持统信 UOS 平台操作系统：observer 与 obproxy 全面兼容主流 X86 平台操作系统。兼容列表详见：https://github.com/oceanbase/oceanbase

• 增强管理员工具 ob_admin：支持解析和显式输出 block_file 文件、归档文件、备份元信息和数据。命令输入形式为ob_admin dumpsst/archive_tool/dump_backup，详细参考帮助命令。

• 完善 OceanBase 社区版本文档。文档包括架构设计原理、性能调优、故障处理、日常维护指导等。

问题修复：

• 修复 __all_virtual_memory_info 虚拟表因 MEMOEY APPEND 失败导致显示租户信息不全的问题。
• 修复因 kill observer 实例导致创建 GLOBAL INDEX 失败的问题。该场景下系统自动发起DDL操作重试保证索引创建成功。
• 修复写入超长列值触发的 SCHEMA 刷新的防御性报错。
• 修复在 CentOS 8.3 和 7.9 平台上的编译错误。更多信息，参考 Issue 714 和 Issue 715。

RELEASE NOTE

About this version

This version fixed some bugs.

BUGFIX

• Fixed start service failure when slog uses more than 80% disk space(#8c615943);
• Fixed process hangs issue when de-duplicating unique indexes by using rowkey comparison(#6dd10291);

发布说明

发版目的

本次发版主要是BUG修复。

BUG 修复

• 修复slog所在的磁盘使用超过80%可能无法启动的问题（ #8c615943）；
• 修复多个唯一索引去重使用rowkey比较时可能会线程hung的问题（ #6dd10291）；

RELEASE NOTE

About this version

In V3.1.1, we have strengthened OceanBase in these fields: kernel compatibility, tools, interfaces, backup and recovery, open-source OS, usability. We will continue to enhance the open-source productization capabilities. Core enhancements and improvements are as follows.

1. MySQL compatibility: Supported MySQL5.7 driver protocol, Common Table Expression (CTE), several compatible functions. And supported migrating data from MySQL OceanBase Database directly.
2. High availability: Supported for physical backup and recovery, cluster-level backup, and tenant-level recovery. You can back up production data at high speed and flexibly select recovery methods according to scenarios and needs.
3. Usability: Released administrator tool ob_admin and error code parsing tool ob_error to provide more convenient and flexible problem analysis and processing capabilities. OBD supported deployment based on system resources and multiple Benchmark testing frameworks.
4. Interface: Released TABLE API interface, supported direct KV access, high-performance storage access. Released REDO log interface CDC, you can connect your data with third-party data easily to do data conversion, extraction, and framework synchronization.
5. Tools: Supported Prometheus, production system operation, and maintenance monitoring. Supported Dbeaver, developer client tools, DataX, Canal, Dataworks data development governance framework, MySQL, and OceanBase data migration. Released small-size Docker. Supported almost all major Linux distributions and installation and deployment for 8+ distributions of OS and 12+ versions.

New features

• Supported physical backup and recovery. OceanBase Database supports physical backup for clusters. Physical backup has sstable and memtable. OceanBase Database supports recovery for tenants. To recover data, you must create a new tenant.
• Supported MySQL 5.7 driver protocol.
• Supported Common Table Expressions (CTE). A CTE is a named temporary result set that exists within the scope of a single statement and that can be referred to later within that statement, possibly multiple times. OceanBase Database syntax is compatible with MySQL 8.0. OceanBase Database supports recursive CTE and non-recursive CTE. For information, see PR 314.
• Supported system function CRC32(). You can calculate the cyclic redundancy check value of a given string. For example, SELECT CRC32("abc");. For information, see PR 152.
• Supported system function CONVERT_TZ(). This function converts a datetime value dt from the time zone given by from_tz to the time zone given by to_tz and returns the resulting value. For example,SELECT CONVERT_TZ('2021-01-01 12:00:00','+00:00','+08:00');. For information, see PR 276.
• Supported INET_ATON(), INET_NTOA(), INET6_ATON(), INET6_NTOA(), IS_IPV4(), IS_IPV6(), IS_IPV4_MAPPED(), and IS_IPV6_MAPPED(). For information, see PR 198.
• Supported the maximum connection setting for tenants/users. Use the system variable MAX_CONNECTIONS to set the maximum connection for tenants. Use the system variable MAX_USER_CONNECTIONS to set the maximum connection for users. When you create a user, use MAX_USER_CONNECTIONS to set the maximum concurrent connection for a specified user. MAX_CONNECTIONS_PER_HOUR specifies the maximum connection per hour for a user.

Tools

• Released Change Data Capture (CDC). CDC is an open-source interface for OceanBase Database. It gives external access to the transaction logs. As a part of the data link, CDC parses, extracts, and assembles the transaction logs. It gives data for downstream data replication. For example, together with Canal, CDC supports incremental data migration.
• Released open-source interface TABLE API. OceanBase database supports access using the NoSQL interface. TABLE API interface is an operational interface for table model and KV model data. It defines a common set of interaction protocols between the client and the database server. The row operation interface supports execute() for single-row operations and batch_execute() for multi-row batch operations. TABLE API supports retrieve/get, insert_or_update/put, delete, insert, update, replace, increment, and append operations.
• Supported data replication tools Canal and DataX. You can replicate data from MySQL to OceanBase Database. You can use DataX to do full data migration to OceanBase Database.
• OBD supported auto test. We integrated mysql_test, TPCH, and Sysbench test frames to OBD. For more information, see OBD test commands.
• OBD supported auto OceanBase Database configuration based on your system resource. Use obd cluster autodeploy to auto deploy OceanBase Database with your maximum available resource. Use obd cluster tenant create/drop to create or drop a tenant. For more information, see OBD cluster tenant create.
• Supports deploying OceanBase Database by using Docker. For more information, see OceanBase Docker Hub.
• Supported DBeaver client. For more information, see PR 13596.
• Supported Prometheus to monitor clusters for the community version. For example, you can monitor your resource (CPU, memory, IO, and net), your system pressure (SQL latency, live session, and cache hit ratio), and cluster usage limits (NTP).
• Supported multiple x86 operation systems. For more information, see Compatibility list.
• Released error code tool ob_error. By using ob_error, you can locate the help information based on the error code returned by OceanBase Database. For more information, see ob_error.
• Released admin tool ob_admin. ob_admin supports parsing transaction logs and transforming transaction ID. The output format is ob_admin clog_tool/usec_tools <args>. For more information, seeclog_tool.

Compatibility changes

| Parameter name | Original default value | Modification type | New default value | Description | | ------------------------------ | -------- | -------------------------- | -------- | ------------------------------------------------------------------------------ | | minor_freeze_times | 5 | Modification | 100 | Avoid triggering frequent merges | | freeze_trigger_percentage | 70 | Modification | 30 | Reduce the risk of excessive cluster memory consumption. Decreasing this value dumps earlier to release memory, but dumping becomes more frequent. | | enable_merge_by_turn | TRUE | Modification | FALSE | By default, we recommend that you merge multiple zones at the same time. Merging by turn needs different zones to avoid response time increase during merges. | | trace_log_slow_query_watermark | 100ms | Modification | 1s | The original default value 100ms is not reasonable. The performance decreases in high pressure. | | clog_sync_time_warn_threshold | 100ms | Modification | 1s | The original default value 100ms is not reasonable. The performance decreases in high pressure because too many log files are produced. | | enable_one_phase_commit | TRUE | Modification | FALSE | Deprecated in the new version. | | enable_pg | FALSE | Deletion | -- | Deprecated in the new version. | | _enable_split_partition | FALSE | Deletion | -- | Deprecated in the new version. |

Bug fixes

• Fixed the problem of using the aggregation function and the same alias. When you use an aggregation function for a string, and you set the result alias the same as the function name, the aggregation function throws an error. For more information, see Issue 173.
• Fixed the problem of timediff precision. When your data has more than 2 digits, the calculation result is NULL. For more information, see Issue 298.

发布说明

版本新特性

本次迭代版本（v3.1.1），OceanBase 全面提升内核兼容、工具生态、接口开放、备份恢复、开源 OS 支持和易用性能力，持续增强开源产品化应用能力。您可以获得以下关键特性：

• 支持 MySQL 5.7 驱动协议，支持 5.7 新增的会话变量。可以推高 OceanBase 的 MySQL 兼容版本，避免企业内部安全审计问题。
• 新增 MySQL 8.0 的通用表表达式（Common Table Expressions），丰富了 SQL 的能力，满足复杂业务查询需求实现。
• 新增校验函数（CRC32()），完善 MySQL 数据迁移到 OceanBase 的数据校验环节。
• 新增物理备份和恢复功能，支持近实时的数据备份和恢复到历史任意时间点功能，提升社区版的容灾能力。
• 新增 TABLE API 接口，支持 KV 接口读写数据，提升高性能存储访问能力。
• 新增 REDO 日志接口 CDC 能力，方便用户抽取 OceanBase 增量数据和跟第三方数据同步产品对接，解决了数据实时流出 OceanBase 难题。
• 支持对接 Prometheus ，提升性能监控和诊断能力。
• 新增管理员工具 ob_admin 和 ERROR CODE 解释工具 ob_error，提升问题排查分析和故障应急处理能力。
• OBD 新增命令参数，支持自动配置相关参数；新增租户管理命令；新增常用数据库性能测试框架，方便初次使用 OceanBase 。

新增功能

MySQL兼容：

• 适配支持 MySQL 5.7 驱动协议，支持 5.7 新增的会话变量。可以推高 OceanBase 的 MySQL 兼容版本，避免企业内部安全审计问题。
• 支持通用表表达式（Common Table Expressions）。语法兼容 MySQL 8.0，支持非递归 CTE 和递归 CTE。CTE 相当于一个临时表但没有实际存储，仅在查询执行期间被使用，丰富了 SQL 的功能。详细信息，参考 PR 314。
• 支持系统函数 CRC32()。您可以通过计算字符串的 CRC32 校验和来校验数据。例如 SELECT CRC32("abc");。详细信息，参考 PR 152。
• 支持系统函数 CONVERT_TZ()。此函数可以实现时区转换查询。例如 SELECT CONVERT_TZ('2021-01-01 12:00:00','+00:00','+08:00');。详细信息，参考 PR 276。
• 支持网络地址相关函数 INET_ATON()、INET_NTOA()、INET6_ATON()、INET6_NTOA()、IS_IPV4()、IS_IPV6()、IS_IPV4_MAPPED() 和 IS_IPV6_MAPPED()。详细信息，参考 PR 198。
• 支持租户/用户最大连接数设置。系统变量 MAX_CONNECTIONS 设置租户最大连接数。系统变量 MAX_USER_CONNECTIONS 设置用户最大并发连接数。创建用户时，可以通过参数 MAX_USER_CONNECTIONS 指定用户的最大并发连接数。参数 MAX_CONNECTIONS_PER_HOUR 指定用户的每小时最大连接数。

高可用性：

• 支持物理备份与恢复。物理备份是集群级别的，包括数据全量和增量备份、事务日志近实时备份（秒级别触发）；物理恢复是租户级别的，能恢复到历史任意时间点（几秒之前）。详细信息，参考 物理备份与恢复。

易用性：

• OBD 支持根据系统资源情况自动配置 OceanBase 参数。新增 obd cluster autodeploy 命令，支持自动使用最高规格启动 OceanBase 数据库。新增 obd cluster tenant create/drop 命令支持创建/删除租户。详细信息，参考 OBD 创建租户。
• OBD 支持自动化测试。OBD 支持集成运行 mysql_test、TPCH 和 Sysbench 测试框架。详细参考帮助命令。详细信息，参考 OBD 测试命令。
• 新增错误码解析工具 ob_error。ob_error 可以帮助您根据 OceanBase 数据库返回的错误码快速找到帮助信息，输入形式为 ob_error [option] errorcode。详细信息，参考 错误码工具。
• 新增管理员工具 ob_admin。ob_admin 支持解析事务日志和转换事务 ID ，提升疑难问题分析诊断能力。输入形式为ob_admin clog_tool/usec_tools <args>。详细信息，参考 clog_tool。

接口开放：

• 开源 TABLE API 接口。OceanBase 数据库支持使用 NoSQL 接口访问。TABLE API 接口是表模型和 KV 模型数据的操作接口，定义了客户端和数据库服务端之间的一组通用的交互协议。行操作接口支持 execute() 执行单行操作和 batch_execute() 执行多行批量操作。支持 retrieve/get、insert_or_update/put、delete、insert、update、replace、increment 和 append 操作。
• 开源 Change data capture（CDC）。CDC 是 OceanBase 数据库对外提供事务日志访问的接口。作为数据链路的一环，CDC 支持解析、抽取和组装事务日志，为下游数据同步提供消费数据。例如，CDC 与 Canal 对接可以实现数据增量迁移。

社区生态

• 支持数据同步工具 Canal 和 DataX。支持将数据从 MySQL 迁移到 OceanBase 数据库。支持使用 DataX 向 OceanBase 数据库全量迁移数据。详细信息，参考 使用 DataX 向 OceanBase 数据库全量迁移数据 和 使用 Canal 向 OceanBase 数据库增量迁移数据。
• 支持 Prometheus 监控系统。增强了社区版本集群监控能力。例如，资源使用监控（包括CPU、内存、IO 和网络）、系统压力监控（SQL 时延、活跃会话和 CACHE 命中率等）、集群使用约束（NTP 时钟同步等）。
• 支持客户端工具 DBeaver。详细信息，参考 文档TODO 和 PR 13596。
• 支持使用 Docker 部署 OceanBase 数据库。详细信息，参考 使用 Docker 部署 OceanBase 数据库。
• 支持多个 x86 平台操作系统。详细信息，参考 兼容性列表。

兼容性变化

| 配置项 | 原默认值 | 修改类型 | 新默认值 | 描述 | | ------------------------------ | -------- | -------------------------- | -------- | ------------------------------------------------------------------------------ | | minor_freeze_times | 5 | 修改 | 100 | 增加内存转储次数，避免内存合并被触发，提升大批量写时性能稳定性 | | freeze_trigger_percentage | 70 | 修改 | 50 | 降低内存转储触发阈值，增加内存转储频率，避免内存写不足报错 | | enable_merge_by_turn | TRUE | 修改 | FALSE | 关闭按 ZONE 逐个合并机制，避免不必要的主备切换带给业务的影响 | | trace_log_slow_query_watermark | 100ms | 修改 | 1s | 增加慢查询 SQL 的时间阈值，减少慢查询日志，降低对磁盘的 IO 影响 | | clog_sync_time_warn_threshold | 100ms | 修改 | 1s | 增加 clog 同步告警时间阈值，减少同步日志 | | enable_one_phase_commit | TRUE | 修改 | FALSE | 新版本已废弃使用 | | enable_pg | FALSE | 删除 | -- | 已废弃的功能 | | _enable_split_partition | FALSE | 删除 | -- | 已废弃的功能 |

Bug 修复

• 修复聚合函数与别名相同使用报错的问题。对某字段使用聚合函数后，对结果设置成相同字段别名后，使用聚合结果排序必须使用别名，不能使用原来的聚合函数排序。详细信息，参考 Issue 173。
• 修复 timediff 精度的问题。当数据的小数点超过 2 位时，计算结果为 NULL。详细信息，参考 Issue 177。
• 修复跨图查询视图报错的问题。详细信息，参考 Issue 298。

RELEASE NOTE

Fixed:

• Fixed the COM_STMT_SEND_LONGDATA error and crash when Golang calls ps.
• Fixed an issue of accessing arrays outside the bounds of numeric objects.

Feature enhancement:

• Improved location refresh mechanism to reduce the response time to failures.
• Set _ob_enable_prepared_statement to false by default.
• Optimized the frequency of writing checkpoint logs for cold partitions.
• Supported PI() function in MySQL tenant.
• Supported transaction_read_only parameter configuration in MySQL tenant.
• Improved the performance for the 'union all' operator.

发布说明

问题修复：

• 修复Golang 驱动在使用ps调用时遇到的COM_STMT_SEND_LONGDATA错误和程序崩溃问题。
• 修复访问数字对象的边界外的数组问题。

特性更新：

• 改善location 刷新机制，降低由于故障导致的交易响应时间变长。
• 设置 _ob_enable_prepared_statement 默认值为false。
• 优化冷分区写checkpoint日志的频率。
• mysql 租户支持PI()函数。
• mysql 租户支持 transaction_read_only 参数配置。
• union all算子性能提升。

Fix:

• Fixed OBserver init io error(#84).
• Fixed plan cache memory leak.
• Fixed compilation and spelling error.

Feature enhancement:

• Supported Debian and SUSE based.