Apache Doris

Supermetal replicates to Apache Doris and VeloDB through Stream Load, or through the S3 table function when data is staged in an object store buffer. Tables with primary keys land as Unique Key with Merge-on-Write.

Prerequisites

• VeloDB Cloud or Apache Doris 4.0 or higher.
• An account with Admin_priv (typically the built in root), since the setup steps issue CREATE USER, CREATE DATABASE, and GRANT.
• Network access from the Supermetal agent to FE HTTP (default 8030, the Stream Load entry point), BE HTTP (default 8040, where Stream Load's 307 redirect lands), and FE MySQL (default 9030, used for SQL and schema reflection).

Setup

mysql -h <fe-host> -P 9030 -u root -p

CREATE USER 'supermetal_user' IDENTIFIED BY 'strong-password';

CREATE DATABASE IF NOT EXISTS target_database;

GRANT SELECT_PRIV, LOAD_PRIV, ALTER_PRIV, CREATE_PRIV, DELETE_PRIV
  ON target_database.*
  TO 'supermetal_user';

CREATE USER 'supermetal_user' IDENTIFIED BY 'strong-password';

CREATE DATABASE IF NOT EXISTS target_database;

GRANT SELECT_PRIV, LOAD_PRIV, ALTER_PRIV, CREATE_PRIV, DELETE_PRIV
  ON target_database.*
  TO 'supermetal_user';

Table Model

Binary Handling

Doris has no native binary type, so BINARY payloads land in STRING. The binary handling mode controls the encoding.

Table Naming

Target table names carry the source schema as a prefix by default, so public.users becomes public_users. Turning the schema prefix off writes to users instead, which is safe only when table names are unique across all source schemas. Independently, you can add a custom prefix or suffix to every table name (raw_users, users_log).

Data Types Mapping