Skip to content

Commit 7557a66

Browse files
authored
Update get-started-change-data-capture.md
1 parent 8e60bb0 commit 7557a66

File tree

1 file changed

+10
-20
lines changed

1 file changed

+10
-20
lines changed

articles/cosmos-db/get-started-change-data-capture.md

Lines changed: 10 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -108,28 +108,18 @@ Now create and configure a source to flow data from the Azure Cosmos DB account'
108108
| Batchsize in bytes | Specify the size in bytes if you would like to batch the change data capture feeds |
109109
| Extra Configs | Extra Azure Cosmos DB analytical store configs and their values. (ex: `spark.cosmos.allowWhiteSpaceInFieldNames -> true`) |
110110

111-
### Working with intermediate updates
111+
### Working with source options
112112

113-
When you check the `Capture intermediate updates`, all versions of updates, and deletes are captured and persisted on the sink. This option creates and populates the `__usr_opType` field in sink with the following values:
114-
115-
| Value | Description |
116-
| --- | --- |
117-
| 1 | UPDATE |
118-
| 2 | INSERT |
119-
| 3 | USER_DELETE |
120-
121-
### Working with intermediate updates and TTL
122-
123-
If you have to identify the TTL deleted records from documents deleted by users or applications, you have check both `Capture intermediate updates` and `Capture Transactional store TTLs` options. This will creates and populates the `__usr_opType` field in sink with a fourth value:
124-
125-
| Value | Description |
126-
| --- | --- |
127-
| 1 | UPDATE |
128-
| 2 | INSERT |
129-
| 3 | USER_DELETE |
130-
| 4 | TTL_DELETE |
113+
When you check any of the `Capture intermediate updates`, `Capture Deltes`, and `Capture Transactional store TTLs` options, your CDC process will create and populate the `__usr_opType` field in sink with the following values:
114+
115+
| Value | Description | Option
116+
| --- | --- | --- |
117+
| 1 | UPDATE | Capture Intermediate updates |
118+
| 2 | INSERT | There isn't an option for inserts, it's on by default |
119+
| 3 | USER_DELETE | Capture Deletes |
120+
| 4 | TTL_DELETE | Capture Transactional store TTLs|
131121

132-
With this information you can create queries and processes to differentiate the deletes performed by an user or application from the deletes caused by TTL operations.
122+
If you have to differentiate the TTL deleted records from documents deleted by users or applications, you have check both `Capture intermediate updates` and `Capture Transactional store TTLs` options. Then you have to adapt your CDC processes or applications or queries to use `__usr_opType` according to what is necessary for your business needs.
133123

134124

135125
## Create and configure sink settings for update and delete operations

0 commit comments

Comments
 (0)