Destinations
Starting Release 2.17, Hevo has stopped supporting Firebolt as a Destination type. As a result, you will not be able to configure new Firebolt Destinations. Any existing Pipelines will continue to be supported. You can also create new Pipelines with your existing Firebolt Destination.
A Destination is any database or data warehouse to which you want to replicate your data. You can configure multiple Pipelines with the same Destination. You can also replicate data from multiple Sources into the same Destination. The data is loaded from all the Pipelines as per the replication schedule you configure for the Destination.
Note: You can use both Hevo UI and API to create Destinations.
You can view the current status of Events being loaded to a Destination by using:
-
The Load Status page in the Pipelines Detailed View: This page displays the number of Events being loaded to the Destination by the specific Pipeline.
-
Destination Overview page in the Destinations Detailed View: This page displays the status of Events being loaded to the Destination from all Pipelines using that Destination.
Note: Ensure that your Destination is configured correctly. If you try to replicate your data in an inactive or deleted database or data warehouse, the data replication fails.
Once your data is loaded to the Destination, you can use Models to transform the data and present it in a format according to your business requirements. Read SQL Models and Working with SQL Models for more information on transforming your Destination data.
- Articles in this section
- Familiarizing with the Destinations UI
- Cloud Storage-Based
- Databases
- Data Warehouses
- Amazon Redshift
- Amazon Redshift Serverless
- Azure Synapse Analytics
- Databricks
- Firebolt
- Google BigQuery
- Hevo Managed Google BigQuery
- Snowflake
- Destination FAQs
- Can I change the primary key in my Destination table?
- How do I change the data type of a Destination table column?
- Can I change the Destination table name after creating the Pipeline?
- How can I change or delete the Destination table prefix after creating a Pipeline?
- Why does my Destination have records that are deleted in the Source?
- How do I filter deleted Events from the Destination?
- If I remove Hevo metadata columns from the Destination table, are these regenerated in the next load?
- How do I filter out specific fields before loading data to the Destination?