Objects and Event Types

An object is an entity in your Source application or database that holds the data Hevo must fetch. For example a collection in your MongoDB instance or a table in your SQL database forms an object. Hevo fetches the data contained in the collection or the table and loads it to the Destination. You can select the required objects to manage the data flow as per your business need. Read Pipeline Objects. You can perform various actions for each object such as queue the tasks related to it, view a sample of its ingested Events, and pause or resume the data ingestion. Read Managing Objects in Pipelines.

The ingested object from your Source is called an Event Type in Hevo. If an object contains just one Event, the object itself becomes the Event Type. Suppose your Source contains 10 objects and you choose only seven for ingestion, then those seven objects become the Event Types once their Events get ingested.

The number of Event Types that are ingested could be greater than the objects. This is because, new Event Type may get created through Transformations you perform to change their properties or based on the strategy you choose for parsing the JSON Events they hold.

You can view the details of each Event Type via the Schema Mapper page. It displays the list of generated Event Types, the Destination table they are being loaded to, and the Source and Destination field mapping for each Event Type. You can perform actions on an Event Type to control how its Events are loaded to the Destination. Read Actions for an Event Type.