ODP Community Edition V4.3.1|V4.3.1| docs|Distributed Database

ODP Community Edition V4.3.1

Last Updated：2025-03-21 09:03:28 Updated

Version information

Release date: August 06, 2024
Version: V4.3.1
RPM version: obproxy-ce-4.3.1.0-4

Overview

OBKV capabilities are supported. For more information, see RPC service port.
Port 2884 of OceanBase Database Proxy (ODP) provides statistics on new connections.
ODP of this version is compatible with the SERIAL data type of MySQL 5.7.
Command words related to communication protocols are supplemented.
Implementation of the compression protocol is optimized, improving the stability of the OceanBase 2.0 protocol.
Parameter configurations are optimized.
System variables such as server_id and server_uuid can be forwarded to binlog instances.
Attributes such as client_ip and proxy_version can be passed to binlog instances in handshake responses.
The action to take after an ODP memory overrun occurs is changed.
Prometheus monitoring for ODP is improved.
MySQL commands such as BINLOG, SHOW RELAYLOG EVENTS, SHOW SLAVE HOSTS, and SHOW SLAVE STATUS are mocked. For more information, see Compatible MySQL commands.
You can specify multiple domain names and addresses for the binlog_service_ip parameter. For more information, see binlog_service_ip.
The CPU utilization of ODP is reduced in standalone mode.
Table locks are supported.
The architecture of primary/standby tenants of OceanBase Database V4.x is supported. For more information, see Automatic routing to the primary/standby tenants.
The ASCII character set is supported.
The utf8mb4_0900_ai_ci collation of the utf8mb4 character set is supported.
You can specify multiple zones for the proxy_primary_zone_name parameter. For more information, see proxy_primary_zone_name.
ODP of this version can identify statements involving DBLinks, avoiding distributed transaction routing.
Complete ObTableLSOpRequest capabilities are supported.
ODP of this version supports returning one result for a batch request or an ObTableLSOpRequest request.
Table groups are supported in HBase mode, so as to support multiple column families.
Request routing information can be obtained in batches in OBKV.
Request protocol parsing is optimized to simplify the parsing process in OBKV.
The dummy_ldc on which requests depend is optimized in OBKV.
In OBKV, session information is decoupled from connections and the routing logic is optimized.
If OBKV-HBase is connected through ODP, substring-based KEY partition routing is supported.
A generated column obtained by using the SUBSTRING_INDEX function can be used as a partitioning key in HBase.

Bug fixes

Fixed the issue where the login fails because configurations cannot be normally written due to concurrent MetaDB parameter update and root@proxyro password update.
Fixed the issue where Prometheus outputs incorrect database names.
Fixed the issue of ObLatch locking failures.
Fixed the issue where the execution of the LOAD DATA LOCAL statement is stuck.
Fixed the issue where data fails to be imported by using obloader V4.3 in direct load mode.
Fixed the issue where verification fails because an invalid session ID is returned after the Java client initiates an asynchronous query.
Fixed the issue where no server error code is returned after a cross-partition request times out.
Fixed the suspected memory leak issue of the OB_CONCURRENCY_OBJ_POOL module in ObTableLSOpRequest disaster recovery scenarios.
Fixed the memory leak issue of the OB_SE_ARRAY module in ObTableLSOpRequest disaster recovery scenarios.
Fixed the issue where a core dump is generated for ODP when a query times out because the client is modified.
Fixed the issue where the execution of the BEGIN statement by the JDBC driver is stuck when both the PreparedStatement and PrepareExecute protocols are enabled for ODP to connect to an OceanBase cluster.
Fixed the issue where connection to a created standby cluster fails with the error cluster name does not match to returned.
Fixed the issue where a binlog does not contain the connection attribute.
Fixed the issue where, after the connection for executing the COM_STMT_SEND_LONG_DATA command is terminated, ODP must terminate the connection with the client.