jprdonnelly/airbyte
1
0
Fork 0
mirror of synced 2025-12-23 21:03:15 -05:00
Code Issues Packages Projects Releases Wiki Activity

📚 Documentation November 2023 overhaul (#32811)

Browse Source 
Co-authored-by: Natalie Kwong <38087517+nataliekwong@users.noreply.github.com>
Co-authored-by: timroes <timroes@users.noreply.github.com>
Co-authored-by: nataliekwong <nataliekwong@users.noreply.github.com>
This commit is contained in:
Tim Roes
2023-11-26 20:57:38 +01:00
committed by GitHub
parent 6fce769ce3
commit c5db1e947b
136 changed files with 1078 additions and 4967 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/connector-development/connector-builder-ui/record-processing.mdx
View File

@@ -321,7 +321,7 @@ Besides bringing the records in the right shape, it's important to communicate s
### Primary key
The "Primary key" field specifies how to uniquely identify a record. This is important for downstream de-duplication of records (e.g. by the [incremental sync - Append + Deduped sync mode](/understanding-airbyte/connections/incremental-append-deduped)).
The "Primary key" field specifies how to uniquely identify a record. This is important for downstream de-duplication of records (e.g. by the [incremental sync - Append + Deduped sync mode](/using-airbyte/core-concepts/sync-modes/incremental-append-deduped)).
In a lot of cases, like for the EmailOctopus example from above, there is a dedicated id field that can be used for this purpose. It's important that the value of the id field is guaranteed to only occur once for a single record.