Schema Mapper

Hevo ingests your data from sources, applies transformations on it and brings it to Schema Mapper. In Schema Mapper you can define how your data will be stored in your destination warehouse.

You can use Hevo’s Schema Mapper to do the following:

  • Map an incoming event type to a destination table. All the data for that event type will be stored in the mapped destination table.
  • Omit unwanted fields from storing in the destination table. This is especially useful to hide sensitive information like your user’s personal details and financial information. You can also use it to omit large text fields like descriptions, summaries, and comments.
  • Flatten your nested objects into a de-normalized destination table. Mapper automatically suggests a denormalized flat structure for your incoming nested objects.
  • Compress long names of Events and Event Types meaningfully to fit the character limit set for table and column names in the Destination.

Apart from giving you the above functionalities, Schema Mapper can also do the following for you:

  • Create tables with compatible and optimal data types in your destination warehouse.
  • Mark incompatible incoming events as Failed for investigation.

Hevo can automatically create and manage all Mappings if you enable Auto Mapping for a pipeline. However, if you wish to manage mapping for a pipeline manually, read Using Schema Mapper. Note: Hevo validates the length of the name even during manual creation of Destination tables and columns. An error is displayed if the length exceeds the defined limit.

Last updated on 14 Sep 2020
Was this page helpful?

Thank you for helping improve Hevo's documentation. If you need help or have any questions, please consider contacting support.