@david.nault I think i got it but the sequence number that you are talking about is the bySeqNo in the kafka connector right? So if i enable persistence polling, then i have to compare the bySeqNo in the messages to get the latest version of the document is my understanding.
I.e.If there is a JSON document with the key 100, then i change the document 5 times. So these are 5 different mutation events in the kafka connector. So i can use the bySeqNo to get the latest and persistence polling would help in the failover scenario as well. Hope this understanding is correct.
I am not sure why you are talking about revSeqNo in theother thread though. I always thought that the sequence number that Couch increases for every change in the document (per vBucket increasing seq number) is same as the bySeqNo. I am a little confused with the point on revSeqNo in the other thread.