When used with mysql as a source, and using the cursor option as opposed to bing logs, how does _airbtyte_extracted_at work? Is it the current datetime on update or insert of record?_

The knowledge sources do not explicitly describe the exact behavior of

_airbyte_extracted_at

specifically for MySQL with cursor-based (non-CDC) incremental sync. However, based on the general Airbyte documentation available, here is what can be stated with confidence:

_airbyte_extracted_at

is NOT the timestamp of the insert/update on the source. It is the timestamp of when Airbyte pulled the record from the data source during a sync operation. [Airbyte metadata fields] So to directly answer your question: • It reflects when Airbyte extracted the record, not when the record was created or updated in MySQL. • If a record was updated in MySQL at 9:00 AM but Airbyte ran its sync at 11:00 AM,

_airbyte_extracted_at

would be approximately 11:00 AM — the time of the sync run. The cursor field (e.g.,

updated_at

on your MySQL records) is what tracks when the record was last changed on the source. Airbyte uses the cursor field to determine which records are new or updated since the last sync, but

_airbyte_extracted_at

is a separate, Airbyte-managed metadata column that simply records the extraction time. [Incremental sync tutorial] In summary: 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help., with interactive elements

@kapa.ai Can you change how airbyte_extract_at behaves?

Based on the available knowledge sources, there is no information suggesting that

_airbyte_extracted_at

is configurable or that its behavior can be changed. It is a framework-managed metadata column that Airbyte automatically appends to every record. [Airbyte metadata fields] Since it is managed internally by Airbyte to record the extraction timestamp, it is not something users can override or customize. If you have a specific use case in mind (e.g., you want to track when a record was last modified at the source), the right approach would be to use a cursor field on your MySQL table (such as

updated_at

) rather than relying on

_airbyte_extracted_at

for that purpose. I'd recommend reaching out to the Airbyte community on Slack or checking the Airbyte GitHub issues if you need more specific guidance on this behavior. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.