Handling of Updates

Most of the Destinations in Hevo are SQL data warehouses where the data is organized in tables. Due to the very basic nature of warehouses, they do not always support updating previously saved Events. However, many of our users want to replicate mutable data into their warehouses for real-time analysis and, therefore, being able to update previously saved Events is important.

Hevo supports updating previously saved Events through primary keys. If you define a primary key in a table in your Destination, Hevo does the following while loading an Event into it:

• If the Event has the same primary key value as an existing Event in the Destination table, it updates the existing Event with the new one.

• If the Event has a primary key value not present in the Destination table, it appends the Event in the table.

The same is true when data is loaded through a Pipeline or a Model.