Version information
Release date: February 9, 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 the OB2.0 protocol are fixed. The version is recommended for general businesses.
Enhanced features
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. The value 0 indicates an infinite timeout period, which means not to specify a timeout period. 0 (infinite)
Bug fixes
- Fixed an issue that the behavior of the
getImportedKeysmethod in MySQL mode is different from that in native MySQL. - Fixed an issue that the behavior to export DATATIME fields with the value of "0000-00-00 00:00:00" is not supported in MySQL mode.
- Fixed an issue that an error is returned when the
getDoublemethod obtains data of theFLOATtype by using the binary protocol in Oracle mode. - Fixed an issue that an error is returned because the
ORDER BYkeyword is not added to internal SQL requests of thegetBestRowIdentifiermethod. - Fixed an issue that the load balancing strategy configured by using an extended URL option does not take effect.
- Fixed an issue that an array cannot contain data of the
BLOBtype in Oracle mode. - Fixed an issue that the errors returned by methods such as
SELECT ' 'andgetShort()in MySQL mode are inconsistent with those in the native MySQL driver. - Fixed an issue that the return value of the
ResultSetMetaData.getColumnName()method in MySQL mode is inconsistent with that in the native MySQL driver. - Fixed an issue that a composite index is inserted into rows but the
SELECTstatement returns an error in MySQL mode. - Fixed an issue that after the result set is disabled, the behavior of
getMetaData()in MySQL and Oracle modes is inconsistent with that in the native drivers. - Fixed an issue that after the result set is disabled, the behavior of
getInt()in MySQL and Oracle modes is inconsistent with that in the native drivers. - Fixed an issue that the values returned by methods of the
ParameterMetaDatainterface in MySQL mode are inconsistent with those in the native MySQL driver. - Fixed an issue that the client IP address is transparently transmitted because the
getLocalAddressAPI returns '0.0.0.0' for the rich client.