Azure Event Hubs
Azure Event Hubs is a managed distributed streaming platform.
Features
| Feature Name | Supported | Notes |
|---|---|---|
| Capture deletes | ||
| History mode | ||
| Custom data | check | |
| Data blocking | check | |
| Column hashing | check | |
| Re-sync | check | |
| API configurable | check | API configuration |
| Priority-first sync | ||
| Fivetran data models | ||
| Private networking | ||
| Authorization via API | check |
Setup guide
Follow our step-by-step Azure Event Hubs setup guide to connect Azure Event Hubs with your destination using Fivetran connectors.
Schema information
Fivetran creates one table for each topic.
IMPORTANT: You can choose which topics to sync on the Schema tab in your Fivetran dashboard.
For each table it creates partition, offset, timestamp and key columns where partition and offset are the primary keys. The timestamp column may contain either create_time or log_append_time as per the server configuration.
You can select to sync packed or unpacked messages. For the packed messages, Fivetran syncs the message in value column. The unpacked messages must be in JSON format. For all the first level JSON elements, Fivetran creates a separate column. The column names are formed using value_<element_name> format.
Historical sync
After making the connection, Fivetran starts syncing all available messages from the Kafka topics. It goes to the earliest available offset for each partition of a topic and starts consuming the messages. It loads the messages into the destination. After the retention period the messages are deleted from the Kafka topics. The deleted messages won't be synced so if you happened to re-sync the connector it would only fetch the current available messages.