The Collections spec states: During receipt of the OSO snapshot (i.e. begin received, but not the end) keep track of the greatest seqno received, consider this X.
X = max(X, received message.seqno).
The client must do this tracking for all DCP mutation, deletion, expiration and system events. If the client enabled synchronous replication, they would also need to include DCP prepare and abort messages.
During receipt of the OSO snapshot (i.e. begin received, but not the end) keep track of the greatest seqno received, consider this X.
Analytics DCP client does not consider system events to be within the OSO snapshot tracking, this should be fixed in Neo.
|For Gerrit Dashboard: MB-49729|
|167176,3||Revert "MB-49729: enable receipt of SEQNO_ADVANCED within an OSO snapshot"||master||cbas-core||Status: MERGED||+2||+1|
|167448,3||MB-49729: seqno advancements should be fully encapsulated within oso||master||analytics-dcp-client||Status: MERGED||+2||+1|
|167449,2||MB-49729: enable receipt of SEQNO_ADVANCED within an OSO snapshot||master||cbas-core||Status: MERGED||+2||+1|
|168409,3||MB-49729: handle seqno advancements within an OSO snapshot||master||cbas-core||Status: MERGED||+2||+1|