Firebolt
This page guides you through the process of setting up the Firebolt destination connector.
Prerequisites
This Firebolt destination connector has two replication strategies:
- 
SQL: Replicates data via SQL INSERT queries. This leverages Firebolt SDK to execute queries directly on Firebolt Engines. Not recommended for production workloads as this does not scale well.
 - 
S3: Replicates data by first uploading data to an S3 bucket, creating an External Table and writing into a final Fact Table. This is the recommended loading approach. Requires an S3 bucket and credentials in addition to Firebolt credentials.
 
For SQL strategy:
- Host
 - Username
 - Password
 - Database
 - Account
 - Engine
 
Airbyte automatically picks an approach depending on the given configuration - if S3 configuration is present, Airbyte will use the S3 strategy.
For S3 strategy:
- Username
 - Password
 - Database
 - Account
 - S3 Bucket Name
- See this to create an S3 bucket.
 
 - S3 Bucket Region
- Create the S3 bucket on the same region as the Firebolt database.
 
 - Access Key Id
- See this on how to generate an access key.
 - We recommend creating an Airbyte-specific user. This user will require read, write and delete permissions to objects in the staging bucket.
 
 - Secret Access Key
- Corresponding key to the above key id.
 
 - Host (optional)
- Firebolt backend URL. Can be left blank for most usecases.
 
 - Engine (optional)
- If connecting to a non-default engine you should specify its name or url here.
 
 
Setup guide
- Sign up to Firebolt following the guide
 - Follow the getting started tutorial to setup a database.
 - Create a service account.
 - Create an engine as described in here
 - (Optional) Create a staging S3 bucket (for the S3 strategy).
 - (Optional) Create an IAM with programmatic access to read, write and delete objects from an S3 bucket.
 
Supported sync modes
The Firebolt destination connector supports the following sync modes:
- Full Refresh
 - Incremental - Append Sync
 
Connector-specific features & highlights
Output schema
Each stream will be output into its own raw Fact table in Firebolt. Each table will contain 3 columns:
_airbyte_ab_id: a uuid assigned by Airbyte to each event that is processed. The column type in Firebolt isVARCHAR._airbyte_emitted_at: a timestamp representing when the event was pulled from the data source. The column type in Firebolt isTIMESTAMP._airbyte_data: a json blob representing the event data. The column type in Firebolt isVARCHARbut can be be parsed with JSON functions.
Changelog
Expand to review
| Version | Date | Pull Request | Subject | 
|---|---|---|---|
| 0.2.22 | 2024-10-12 | 46841 | Update dependencies | 
| 0.2.21 | 2024-10-05 | 46420 | Update dependencies | 
| 0.2.20 | 2024-09-28 | 46144 | Update dependencies | 
| 0.2.19 | 2024-09-21 | 45744 | Update dependencies | 
| 0.2.18 | 2024-09-14 | 45562 | Update dependencies | 
| 0.2.17 | 2024-09-07 | 45245 | Update dependencies | 
| 0.2.16 | 2024-08-31 | 44991 | Update dependencies | 
| 0.2.15 | 2024-08-24 | 44698 | Update dependencies | 
| 0.2.14 | 2024-08-22 | 44530 | Update test dependencies | 
| 0.2.13 | 2024-08-17 | 44239 | Update dependencies | 
| 0.2.12 | 2024-08-10 | 43682 | Update dependencies | 
| 0.2.11 | 2024-08-03 | 43143 | Update dependencies | 
| 0.2.10 | 2024-07-27 | 42703 | Update dependencies | 
| 0.2.9 | 2024-07-20 | 42211 | Update dependencies | 
| 0.2.8 | 2024-07-13 | 41789 | Update dependencies | 
| 0.2.7 | 2024-07-10 | 41602 | Update dependencies | 
| 0.2.6 | 2024-07-09 | 41118 | Update dependencies | 
| 0.2.5 | 2024-07-06 | 40854 | Update dependencies | 
| 0.2.4 | 2024-06-27 | 40578 | Replaced deprecated AirbyteLogger with logging.Logger | 
| 0.2.3 | 2024-06-25 | 40494 | Update dependencies | 
| 0.2.2 | 2024-06-22 | 40078 | Update dependencies | 
| 0.2.1 | 2024-06-06 | 39157 | [autopull] Upgrade base image to v1.2.2 | 
| 0.2.0 | 2024-05-08 | 36443 | Service account authentication support | 
| 0.1.1 | 2024-03-05 | 35838 | Un-archive connector | 
| 0.1.0 | 2022-05-18 | 13118 | New Destination: Firebolt |