Does INT Primary Key column is also the valid field instead of date column for the incremental cursor column for Sync mode as "Incremental & Deduped" ?

Based on the provided knowledge sources, an

INT

primary key column is not typically used as a cursor field for incremental sync modes, including "Incremental & Deduped." A cursor field is generally a field that can track changes over time, such as a timestamp. This is because the cursor field is used to determine whether a record should be replicated during an incremental sync. A common example of a cursor field is a timestamp from an

updated_at

column in a database table (see [source](https://docs.airbyte.com/using-airbyte/core-concepts/sync-modes/incremental-append-deduped#definitions)). The primary key, on the other hand, is used to identify unique entities in a table and is crucial for deduplication in the "Incremental & Deduped" sync mode. The primary key ensures that only the most recent version of a record is included in the final deduplicated table (see [source](https://airbyte.com/tutorials/incremental-data-synchronization#step-2)). In summary, while an

INT

primary key column is essential for identifying unique records and deduplication, it is not suitable as a cursor field for incremental syncs. The cursor field should be a column that can effectively track changes over time, such as a timestamp. For more detailed information, you can refer to the following documentation: - [Incremental Sync - Append + Deduped Definitions](https://docs.airbyte.com/using-airbyte/core-concepts/sync-modes/incremental-append-deduped#definitions) - [Why and when is a primary key required](https://airbyte.com/tutorials/incremental-data-synchronization#step-2)