Connector support
This matrix is generated from the maintained capability source and checked against the Java manager registry. Roles describe whether a manager can be a source or sink; source and sink modes are listed separately so a readable source mode is never presented as a sink guarantee. Connector pages add connection, driver, query, job-count, type, staging, and security details.
| Connector | Source modes | Sink modes | Staging | Caveat |
|---|---|---|---|---|
| MySQL | completecomplete-atomicincremental | completecomplete-atomicincremental | Supported where the mode requires it | Uses the MariaDB JDBC driver and supports LOAD DATA style optimizations where available. |
| MariaDB | completecomplete-atomicincremental | completecomplete-atomicincremental | Supported where the mode requires it | Use MariaDB-compatible connection properties and validate server-specific SQL behavior before production runs. |
| PostgreSQL | completecomplete-atomicincremental | completecomplete-atomicincremental | Supported where the mode requires it | Binary COPY is optimized for compatible shapes; complex values may use the text path. |
| HSQLDB | complete | complete | Not provided | The maintained generic path is complete-mode and single-job only. |
| Oracle | completecomplete-atomicincremental | completecomplete-atomicincremental | Supported where the mode requires it | Flashback and partition behavior depend on Oracle permissions and the selected query shape. |
| SQL Server and Azure SQL | completecomplete-atomicincremental | completecomplete-atomicincremental | Supported where the mode requires it | Microsoft Entra interactive authentication requires jobs=1 and is not a headless container flow. |
| CUBRID | complete | complete | Not provided | The maintained generic path is complete-mode and single-job only. |
| jTDS SQL Server | complete | complete | Not provided | This legacy driver path is complete-mode and single-job only; prefer the Microsoft driver for new SQL Server work. |
| IBM Db2 | completecomplete-atomicincremental | completecomplete-atomicincremental | Supported where the mode requires it | Partitioning and type behavior differ between Db2 LUW and other Db2 environments. |
| IBM i Db2 | completecomplete-atomicincremental | completecomplete-atomicincremental | Supported where the mode requires it | Use IBM i naming and permissions appropriate to the AS/400 JDBC driver. |
| Netezza | complete | complete | Not provided | The maintained generic path is complete-mode and single-job only. |
| Denodo | completecomplete-atomicincremental | Not supported | Not provided | Denodo is source-only; it does not implement sink writes or staging. |
| Kafka | Not supported | complete | Not provided | Kafka is sink-only and the maintained capability is complete-mode row publishing. |
| Amazon S3 | Not supported | complete | Not provided | S3 is sink-only and uses the runtime credential chain; it does not provide table merge semantics. |
| CSV and local files | completecomplete-atomicincremental | completeincremental | Supported where the mode requires it | File replication is single-job only and has no complete-atomic sink mode. |
| SQLite | completecomplete-atomicincremental | completeincremental | Supported where the mode requires it | SQLite does not support the complete-atomic sink capability and is constrained by file locking. |
| MongoDB | completecomplete-atomicincremental | completeincremental | Supported where the mode requires it | MongoDB sink mode has no complete-atomic capability; document-to-row mapping is connector-specific. |
| MongoDB SRV | completecomplete-atomicincremental | completeincremental | Supported where the mode requires it | SRV discovery and TLS settings are supplied by the MongoDB connection string and deployment environment. |