Auto Mapping Event Types

Hevo provides you an option to automatically map Event Types and fields in a Pipeline to corresponding tables and columns in the Destination, thereby eliminating the need for any human intervention. You can enable Auto Mapping at the Pipeline or the Event Type level.

Auto Mapping toggle buttons in the UI

Once you configure the Source and Destination of a Pipeline and select Auto Mapping, Hevo replicates the Source schemas as is, and you need not worry about any schema changes in the Source either. Click the VIEW SCHEMA button to see the Source schema details such as the list of objects synced and data types of the fields pertaining to each object.

As part of Auto Mapping, Hevo:

  • Creates the respective tables in the Destination with the appropriate schema if these are not present already.

  • Maps all the Source Event Types automatically to the tables in the Destination.

  • Creates and maps any new fields detected in the Event Types in the corresponding Destination tables.

When a new Event Type is encountered, the respective table is automatically created in the Destination if it is not already present.

For both database and data warehouse Destinations, any primary keys defined in the Source are retained in the Destination tables during Auto Mapping. In addition, for the Amazon Redshift data warehouse, sort keys are automatically created on the primary keys defined for the respective tables. This is similar to the functionality offered in manual schema mapping.

Sort keys created during schema mapping for Amazon Redshift Destination

Note: A sort key defines the column by which data is sorted in a table. Availability of sorted data improves the query efficiency during loading of Events as number of scans required to identify the location of update are substantially reduced. Consequently, job performance is improved.

Last updated on 08 Jul 2021