Hi all, I have a problem with stopping replication.
I have 1 main database containing all data, and then per-user databases containing limited data. The user-databases are filled by filtered continuous replication. Specifically, some user-metadata document for the user is replicated, containing a field for `receivesUpdates`. Now if I turn that field to `false`, I want the replication job to stop immediately, and not send a document anymore. It could be a privacy issue if another document is replicated after setting `receivesUpdates` to `false`. The best I’ve come up with so far is to have a changes-feed listener that stops the replication job when it detects such a change in the main database. But before the replication is stopped, I guess another change might have come through. My question is: is there a solution for this problem? And if not: is that fundamental? Is the changes feed still consistently ordered in a cluster? Thanks in advance, Roald
