This topic describes the features of OceanBase Migration Service (OMS) Community Edition V4.2.9.
Notice
Only OMS Community Edition V4.2.0 to V4.2.8 can be upgraded to OMS Community Edition V4.2.9.
New features
OMS Community Edition V4.2.9 supports data migration from an Elasticsearch database to OceanBase Database Community Edition.
OMS Community Edition V4.2.9 supports data migration from vector and array columns of a PostgreSQL database to OceanBase Database Community Edition.
OMS Community Edition V4.2.9 supports data migration from TiDB V8.x to OceanBase Database Community Edition.
OMS Community Edition V4.2.9 supports migration of dynamic columns from a Milvus database to OceanBase Database Community Edition.
OMS Community Edition V4.2.9 supports data migration from Hive V2.1.1 to OceanBase Database Community Edition.
In a data synchronization task from OceanBase Database Community Edition to Kafka, the task can send ordered heartbeats. Then, the downstream consumers can check whether all the data at a specific point in time is consumed based on the time information in the heartbeat.
OMS Community Edition V4.2.9 supports migration of STRING-type data from OceanBase Database Community Edition.
OMS Community Edition V4.2.9 supports the service_name configuration method for an OceanBase data source.
OMS Community Edition V4.2.9 supports multiple host ports for a Kafka data source.
Usability improvements
When you synchronize data from OceanBase Database Community Edition to Kafka, you can configure table name wildcard mapping for topics.
The database version of an OceanBase data source is automatically refreshed. This prevents OMS from using an incorrect CDC version during incremental synchronization of data from OceanBase Database after the database version is upgraded.
The performance issues of migrating columns with multiple unique keys (UKs) in TiDB in TICDC mode are optimized.
The page for modifying component parameters is optimized.