Conduit Connector Materialize
General
This connector allows you to move data from any Conduit Source to a Materialize Table. This connector is a destination connector.
Prerequisites
Table name
If a record contains a table property in its metadata it will be inserted in that table, otherwise it will fall back to use the table configured in the connector. This way the Destination can support multiple tables in the same connector, provided the user has proper access to those tables.
Known limitations
Materialize doesn't yet support primary keys, unique constraints, and UPSERT. This means there is no guarantee that Materialize will not have duplicates. Delete and update will affect all records found by the specified key and insert only appends data.
Configuration Options
| name |
description |
required |
default |
url |
The connection URL for Materialize instance. |
true |
|
table |
The table name of the table in Materialize that the connector should write to, by default. |
true |
|
key |
The column name used when updating and deleting records. |
true |
|
Testing
Run make test in order to run all the unit and integration tests. This requires Docker to be installed.