Version information
Release date: February 09, 2023
Version: V2.4.2
Overview
OceanBase Connector/J V2.4.2 can obtain OceanBase Database Proxy (ODP) configurations from OceanBase Cloud Platform (OCP) to improve load balancing performance. Some issues related to compatibility and OceanBase Protocol 2.0 are fixed. The version is recommended for general businesses.
Feature enhancements
- OceanBase Connector/J V2.4.2 can obtain ODP configurations from OCP to improve load balancing performance. The following URL parameters are added.
| Parameter | Description | Default value |
|---|---|---|
| ocpAccessInterval | The interval for accessing OCP, in minutes. | 5 |
| httpConnectTimeout | The timeout period for connecting to a network resource over HTTP, in milliseconds. This parameter is set when a communications link to the resource referenced by this URLConnection is opened. |
0 (infinite) |
| httpReadTimeout | The timeout period for reading a network resource over HTTP when the URLConnection to the resource is established, in milliseconds. |
0 (infinite) |
Bug fixes
- Fixed the issue where the behavior of the
getImportedKeys()method in MySQL mode is inconsistent with that in native MySQL. - Fixed the issue where the behavior to export DATETIME fields with the value of "0000-00-00 00:00:00" in MySQL mode is inconsistent with that in native MySQL.
- Fixed the issue where an error is returned when the
getDouble()method obtains data of theFLOATtype by using the binary protocol in Oracle mode. - Fixed the issue where an error is returned because the
ORDER BYkeyword is not added to internal SQL requests of thegetBestRowIdentifier()method. - Fixed the issue where the load balancing strategy configured by using an extended URL parameter does not take effect.
- Fixed the issue where an array cannot contain data of the
BLOBtype in Oracle mode. - Fixed the issue where the errors returned by methods such as
SELECT ' 'andgetShort()in MySQL mode are inconsistent with those in the native MySQL driver. - Fixed the issue where the return value of the
ResultSetMetaData.getColumnName()method in MySQL mode is inconsistent with that in the native MySQL driver. - Fixed the issue where a composite index is inserted into rows but the
SELECTstatement returns an error in MySQL mode. - Fixed the issue where, after the result set is closed, the behavior of
getMetaData()in MySQL and Oracle modes is inconsistent with that in the native drivers. - Fixed the issue where, after the result set is closed, the behavior of
getInt()in MySQL and Oracle modes is inconsistent with that in the native drivers. - Fixed the issue where the values returned by methods of the
ParameterMetaDatainterface in MySQL mode are inconsistent with those in the native MySQL driver. - Fixed the issue where the client IP address is transparently transmitted because the
getLocalAddress()method returns '0.0.0.0' for the rich client.