OceanBase Database Proxy Community Edition V4.4.1

V4.4.1

Version information

• Release date: August 4, 2026

• Version number: V4.4.1

• RPM version number: obproxy-ce-4.4.1.0-1

Overview

ODP V4.4.1 is the latest version in the ODP 4.x series, with a focus on enhancing routing capabilities and weak-consistency read control. It introduces a new feature to transparently pass through Database information in SQL requests. This allows ODP to parse the Database information in SQL requests and pass it through to OBServer via the OB 2.0 protocol. OBServer can then select the corresponding Database resource group to execute the request, achieving Database-level resource isolation. Additionally, support for the /*FORCE_MASTER*/ comment has been added, which forcibly routes weak-consistency read requests to the leader replica, meeting strong-consistency data requirements in specific business scenarios. Furthermore, columnstore replica routing functionality has been introduced, supporting the parsing of columnstore replicas, automatic parameter selection, and combining SQL routing hints to directly route OLAP requests to columnstore replicas, improving query performance in complex analysis scenarios.

Recommended for cloud and on-premises businesses for POC testing and production.

Key features

SQL proxy

• Transparently pass through SQL request's Database information

  In SaaS scenarios, each user corresponds to an independent Database. To avoid resource contention between users, the database must have Database-level resource isolation capability. ODP V4.4.1 introduces a new feature to transparently pass through Database information. It supports parsing the Database information in SQL requests and passing it through to OBServer via the OB 2.0 protocol. OBServer then submits the request to the corresponding resource group for processing based on the binding relationship between the Database and the resource group, thereby achieving Database-level resource isolation. This effectively enhances resource isolation capability and system stability in SaaS scenarios.

• Supports FORCE_MASTER comment

  In the read-write separation architecture of OceanBase Database, to reduce the load on leader replicas, non-transactional read requests are typically routed to follower replicas for execution as weak-consistency reads. However, in business scenarios with high data consistency requirements, such as financial transactions or account queries, users often need to read the latest data. In these cases, weak-consistency reads cannot meet the business needs, and these read requests need to be routed to leader replicas.

  ODP V4.4.1 now supports the /*FORCE_MASTER*/ comment. Users can add this comment before SELECT statements that require strong-consistency reads. After recognition, ODP will forcibly route the request to the leader replica for execution, thereby achieving strong-consistency reads. This comment has a higher priority than the read-write separation routing strategy and does not affect uncommented weak-consistency read requests. With this feature, users can flexibly control the consistency level of read requests at the statement granularity, meeting strong-consistency data requirements in specific business scenarios without adjusting global configurations.

  Usage example:

  /*FORCE_MASTER*/ SELECT * FROM t1 WHERE id = 1;
  

• Supports columnstore replica routing

  In OLAP analysis scenarios, the columnstore engine can significantly improve the execution performance of complex queries. OBServer already supports automatic columnstore replica selection. You can control the related strategy using the ap_query_route_policy parameter, and it can automatically identify AP queries suitable for execution on columnstore replicas based on query characteristics and execution cost.

  To further improve the routing efficiency of analytical requests, ODP V4.4.1 introduces columnstore replica routing functionality. It supports identifying the ap_query_route_policy parameter and columnstore routing hints in SQL statements. For requests that explicitly specify the use of columnstore replicas, ODP can directly route them to columnstore replicas for execution without performing parallelism checks or cost calculations. This improves request processing efficiency in complex analysis scenarios and further reduces query latency.

Compatibility changes

Parameter changes

Supported OBServer versions

ODP supports OBServer 4.x, OBServer 3.x, and earlier versions.

Recommended version

ODP 4.4.1 introduces several new features and enhances stability. If you rely on these new features, we recommend that you use ODP 4.4.1.

Bug fixes

• Fixed an issue where concurrent access to a map without locking caused memory exceptions and occasional ODP core dumps.

• Fixed an issue where the OB_PROXY_SHARDING_EXPR module experienced memory exceptions.

• Fixed an issue where ODP routed incorrectly when different schemas had the same SQL_ID.

• Fixed an issue where an ODP core dump occurred due to a Binlog ResultSet EOF across buffers.

• Fixed an issue where an ODP core dump occurred when the PS was disabled for a cross-tenant service_name connection.

• Fixed an issue where ODP failed to parse table names accurately, leading to inaccurate routing, when comments contained dots.

• Fixed an issue where the random routing overhead in ODP was excessively high.

• Fixed an issue where ODP experienced a core dump due to out-of-bound filling of tenant_name when obtaining a table_entry.

• Added support for routing to INTERVAL partitions.

• Fixed an issue where the LOAD DATA LOCAL INFILE statement failed for large files due to memory exhaustion.