OceanBase
English日本語简体中文
Docs Home
Products
Integrations
Release Notes

Databases

OceanBase DatabaseOceanBase Cloud OceanBase Best Practices

Tools

OceanBase Cloud PlatformOceanBase Migration ServiceOceanBase Developer CenterOceanBase Migration AssessmentOceanBase Admin ToolOceanBase Loader and DumperOceanBase DeployerKubernetes operator for OceanBaseOceanBase Diagnostic Tool OceanBase Binlog Service

Connectors and Middleware

OceanBase Database Proxy OceanBase Connector/C OceanBase Connector/J OceanBase Connector/ODBC OceanBase Connector/NETOceanBase Command-Line Client

Databases

OceanBase DatabaseOceanBase Cloud OceanBase Best Practices

Connectors and Middleware

OceanBase Database Proxy OceanBase Connector/C OceanBase Connector/J OceanBase Connector/ODBC OceanBase Connector/NETOceanBase Command-Line Client

Tools

OceanBase Cloud PlatformOceanBase Migration ServiceOceanBase Developer CenterOceanBase Migration AssessmentOceanBase Admin ToolOceanBase Loader and DumperOceanBase DeployerKubernetes operator for OceanBaseOceanBase Diagnostic Tool OceanBase Binlog Service
OceanBase DatabaseOceanBase Cloud ToolsConnectors and MiddlewareLifecycle Support Policy

OceanBase Cloud

  • Overview
  • Schema evolution
    • Liquibase
    • Flyway
  • Data ingestion
    • Canal
    • dbt
    • Debezium
    • Flink
    • Glue
    • Informatica Cloud
    • Kafka
    • Maxwell
    • SeaTunnel
    • DataWorks
    • NiFi
  • SQL development
    • DataGrip
    • DBeaver
    • Navicat
    • TablePlus
  • Orchestration
    • DolphinScheduler
    • Linkis
    • Airflow
  • Visualization
    • Grafana
    • Power BI
    • Quick BI
    • Superset
    • Tableau
  • Observability
    • Datadog
    • Prometheus
  • Database management
    • Bytebase
  • AI
    • LlamaIndex
    • Dify
    • LangChain
    • Tongyi Qianwen
    • OpenAI
    • n8n
    • Trae
    • SpringAI
    • Cline
    • Cursor
    • Continue
    • Toolbox
    • CamelAI
    • Firecrawl
    • Hugging Face
    • Ollama
    • Google Gemini
    • Cloudflare Workers AI
    • Qoder
    • OpenCode
    • Claude Code
    • GitHub Copilot
    • Codex
    • Jina AI
    • Augment Code
    • Claude Code
    • Kiro
  • Development tools
    • Cloudflare Workers
    • Vercel

Download PDF

Document Feedback
  1. Documentation Center
  2. OceanBase Cloud

Maxwell

Last Updated:2026-09-04 07:03:30

Prerequisites
Procedure

Maxwell reads and converts MySQL binlogs into the JavaScript Object Notation (JSON) format. It is used to capture all data change events in a database. This topic describes how to use Maxwell to export data of a MySQL-compatible tenant of OceanBase Cloud in the JSON format.

Prerequisites

Before you use Maxwell, make sure that the following conditions are met:

  • You have activated the Binlog service for OceanBase Cloud in the MySQL compatible mode. For more information, see Procedure.
  • You have installed Java 1.8 or later.
  • You have downloaded Maxwell. For more information, see the description of Maxwell at GitHub.

Procedure

  1. Activate the Binlog service in OceanBase Cloud. In the left-side navigation pane of the OceanBase Cloud console, choose Instances > Tenant Management and activate the Binlog service. For more information, see Activate the Binlog service.

  2. Configure Maxwell. Edit the config.properties file in the working directory of Maxwell. If this file does not exist, copy config.properties.example, rename it into config.properties, and edit the file.

    user=maxwell
    password=yourpassword
    host=IP address of the server of the source MySQL-compatible tenant of OceanBase Cloud
    producer=stdout
    

    stdout indicates the standard output mode. With this configuration, Maxwell directly exports data to the console. To enable Maxwell to export data to other targets such as Kafka, change the value of producer and related configurations.

  3. Start Maxwell.

    Run the following command to start Maxwell:

    bin/maxwell --config config.properties
    
  4. View data changes Change data in OceanBase Cloud, for example, insert, update, or delete data. Then, observe the JSON data exported by Maxwell. Set the output mode of Maxwell to stdout in the command in Step 3. The possible return results are as follows:

     {
     "database": "mydb",
     "table": "mytable",
     "type": "insert",
     "ts": 1589372847,
     "xid": 12345678,
     "commit": true,
     "data": {
         "id": 1,
         "column1": "value1",
         "column2": "value2"
     }
     }
    

    The return results show that data was inserted into the mydb.mytable table.

Notice

OceanBase Cloud V4.1.0 and later support Latin character sets. If you use OceanBase Cloud of a version earlier than V4.1.0 as the MetaDB for Maxwell, you must manually build the metadata tables of Maxwell.

In the following example, the latin1 character set is deleted from the CREATE TABLE statement of Maxwell.

CREATE TABLE IF NOT EXISTS `databases` (
  id        bigint auto_increment NOT NULL primary key,
  schema_id bigint,
  name      varchar(255) charset 'utf8',
  charset   varchar(255),
  index (schema_id)
);

This example describes how to operate a single metadata table. You need to perform the same operations on other metadata tables.

Previous topic

Kafka
Last

Next topic

SeaTunnel
Next
on this page
Prerequisites
Procedure