Azure / Azure/azure-documentdb-changefeedprocessor-dotnet

Question: Change ordering - will the final version of a document always be presented in the case of an update?

Open
#125 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
51
Forks
24
PR merge metrics
No merged PRs in 30d

Description

Can the ChangeFeed always be relied on to present the final version of a document in its correct sequence ?

i.e. (under the same partition key value) if I insert doc 1 (call that edition 1a), then insert doc 2 in a separate transaction, then insert doc 3 and update doc 1 in the next transaction (1b),

1. am I guaranteed I'll see either: `1a,2,3,1b` or `2,3,1b` ?
2. Can I rule out seeing `1b` ... `1a` ?
3. Can I rule out seeing `1a` but never `1b` ?
4. I am fine with not being guaranteed to see `1a` - but can you confirm this is possible ?
5. I assume if one was to start a new projection N hours/days later, it's highly unlikely to see `1a` ?
6. Can you confirm that one'd never see `1a` presented after `2` or `3` ?

Same questions as above:- even as as Partitions split or merge? (see also #124)

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.