Propel Private Preview
Propel is an Analytics Platform as a Service for developers. It provides serverless ClickHouse Cloud infrastructure, data-serving APIs, and React components to deliver embedded analytics, analytics APIs, and usage metering use cases in record time.
You can use Fivetran to sync data to Propel's serverless ClickHouse Cloud infrastructure for the following use cases:
- To sync data from databases, such as Oracle, MySQL, or PostgreSQL.
- To sync data from SaaS applications or platforms, such as HubSpot, Shopify, or Stripe.
- To sync data from event streaming sources, such as Kafka, Kinesis, or Google Pub/Sub.
NOTE: This destination is partner-built. For any questions related to Propel destination and its documentation, contact Propel Support.
Setup guide
Follow our step-by-step Propel setup guide to connect Propel to Fivetran.
Type transformation mapping
As we extract your data, we match Fivetran data types to types that Propel supports. If we don't support a specific data type, we automatically change that type to the closest supported data type or, in some cases, don't load that data.
All supported data types are valid for primary keys except BOOLEAN and JSON.
The data types in Propel follow Fivetran's standard data type storage.
The following table illustrates how we transform your Fivetran data types into Propel-supported types:
| FIVETRAN DATA TYPE | PROPEL DATA TYPE |
|---|---|
| BOOLEAN | BOOLEAN |
| SHORT | INT16 |
| INT | INT32 |
| LONG | INT64 |
| BIGDECIMAL | DOUBLE |
| FLOAT | FLOAT |
| DOUBLE | DOUBLE |
| LOCALDATE | DATE |
| LOCALDATETIME | TIMESTAMP |
| INSTANT | TIMESTAMP |
| STRING | STRING |
| XML | STRING |
| JSON | JSON |
| BINARY | STRING |
Schema changes
| SCHEMA CHANGE | SUPPORTED | NOTES |
|---|---|---|
| Add column | Yes | When Fivetran detects a column being added to your source, Fivetran automatically adds that column in Propel. |
| Change column type | No | Changing column types is not supported as it is a breaking schema change. |
Limitations
Propel has the following primary key limitations:
- Tables must have a primary key column. Only one column can be set as the primary key.
- Primary keys with BOOLEAN or JSON columns are not supported.
- History mode is not supported.