Setting up SuperDuperDB as a change-data-capture daemon
info
This functionality is currently for MongoDB only
Setting-up SuperDuperDB as a change-data-capture daemon, is a simple call:
db.cdc.listen()
... or
superduperdb cdc
When superduperdb
is configured in this way, this daemon handles all inserts to
SuperDuperDB, therefore, if superduperdb
is run in another process or service,
it's important to configure the existence of the daemon:
from superduperdb import CFG
CFG.cluster.cdc = True
Now that the daemon is running, even when data is inserted using a different client, such as
the native pymongo.MongoClient
client, then Listener
outputs are still created on those inputs.