Materialize
Overview
The Materialize destination lets you load data into a Materialize cluster using its PostgreSQL-compatible interface. This connector is implemented as a Postgres-compatible destination, so configuration and behavior closely match other Postgres-style destinations.
Setup
- Ensure your Materialize region/cluster is reachable from your deployment (network allowlists, VPC peering, etc., as applicable).
- Create (or choose) a database and schema in Materialize where the connector can create and write tables.
- Create a Materialize user with permissions to create and write to tables in the target schema.
Authentication
The connector authenticates with Materialize using standard PostgreSQL connection credentials:
- Host
- Port
- Database
- User
- Password
- SSL mode / TLS settings (as required by your Materialize deployment)
Configuration
Provide the following connection details when configuring the destination:
| Field | Type | Required | Description |
|---|---|---|---|
| Host | string | ✓ | Materialize hostname (for example, xyz.materialize.cloud). |
| Port | number | ✓ | PostgreSQL-compatible port for Materialize. |
| Database | string | ✓ | Target database name. |
| Schema | string | ✓ | Target schema where tables will be created/written. |
| User | string | ✓ | Username used to connect. |
| Password | string | ✓ | Password for the user. |
| SSL mode | string | SSL/TLS requirement (for example, require, verify-full), depending on your environment. |
Hashing and normalization
This destination connector does not currently expose field-level hashing controls in its public configuration.
Data contract
Table creation and writes
- Data is loaded into tables in the configured database and schema.
- The connector uses Materialize’s PostgreSQL-compatible interface to create and write tables as needed.
Type mapping
Materialize is PostgreSQL-compatible, but not all PostgreSQL types and behaviors are identical. If you encounter type-related issues, validate that the target column types are supported by Materialize and adjust upstream typing/casting accordingly.
Notes and limitations
- Connectivity and TLS requirements vary by Materialize deployment. If connections fail, confirm network access and SSL settings.
- Permissions must allow creating and writing tables in the target schema.
Streams
This is a Reverse ETL destination connector. It does not expose source streams.