__artie_ to your destination tables. These columns track how and when each row was changed. You can enable them under your destination’s advanced settings.
History mode columns
These columns are automatically added to tables using history mode. They provide a full audit trail of every change.| Column | Data Type | Description |
|---|---|---|
__artie_operation | STRING | The type of change that was made to the row. Possible values: CREATE, UPDATE, DELETE. |
__artie_updated_at | TIMESTAMP_TZ | The timestamp of when Artie processed the change. |
__artie_db_updated_at | TIMESTAMP_TZ | The timestamp of when the change occurred in your source database. |
Soft delete columns
These columns are added when soft deletes are enabled. Instead of removing deleted rows, Artie flags them so you can retain the data.| Column | Data Type | Description |
|---|---|---|
__artie_delete | BOOLEAN | true if the row was deleted in the source database. |
__artie_only_set_delete | BOOLEAN | S3 destinations only. true if the row was deleted and the event contains no other column values to update — only the delete flag itself. |
What is the difference between __artie_delete and __artie_only_set_delete?
What is the difference between __artie_delete and __artie_only_set_delete?
Both columns indicate a deletion, but they serve different purposes:
__artie_deleteis set totruewhenever a row is deleted.__artie_only_set_deleteis set totruewhen the delete event carries no additional column values — meaning there is nothing to update in the destination besides the delete flag.
__artie_delete = true and __artie_only_set_delete = false.Static columns
Static columns let you add custom key-value pairs to every row written to your destination table. Each static column has a fixed name and value that you define — the value does not change per row. This is useful when you need to tag rows with metadata that isn’t present in the source, such as an environment label, a data source identifier, or a tenant ID. You can configure static columns under your destination’s advanced settings.Source metadata columns
These columns provide context about where each row originated and the underlying database event that produced it. You can enable them under your destination’s advanced settings.| Column | Data Type | Description |
|---|---|---|
__artie_full_source_table_name | STRING | The fully qualified source table name in the format dbName.schemaName.tableName. |
__artie_source_metadata | JSON | Source metadata from the change event, such as the log sequence number (LSN), transaction ID, and other database-specific fields. |