Hevo-generated Metadata (Edge)
Last updated on Sep 25, 2024
Edge Pipeline is currently available under Early Access. You can request access to evaluate and test its features.
In the process of ingesting Events from a database Source or a SaaS Source and uploading them to the Destination, Hevo may add metadata columns to the Destination tables. This depends on the options you specify during Pipeline creation for the ingestion and uploading of the data, and on the nature of the Destination system itself. Some of these columns are transient, while some are permanent.
The following table describes the metadata columns that Hevo generates:
| Metadata Column | Description |
|---|---|
__hevo_ingested_at |
A timestamp that helps to verify that the ingested Event is more current than what already exists in the Destination. |
__hevo_op_type |
This field indicates the type of operation (such as insert, update, or delete) being performed on the Event. It helps determine how the data should be processed in the Destination. |
__hevo_source_modified_at |
A column that logically represents a deleted Event. |
__hevo__is_deleted |
A column that logically represents a deleted Event. |
__hevo_loaded_at |
A timestamp that indicates when data was inserted, updated, or deleted (delete flag updated) in the Destination table. |