The user is required to create this specific bucket in order to let the Couchbase Eventing service to store its own metadata. For our convention this will be the “Metadata bucket” in which the eventing function will store the events metadata. The name can be, for example, “metadata-eventing” or “metadata-bucket” but it is not a constraint, it could be customized in the config file.
Note: you will need 1 of this kind of bucket for all of your eventing functions. So, if you already have some eventing functions deployed into your Couchbase cluster you can use the same bucket.
The Data bucket is the bucket in your Couchbase Cluster that actually contains the data you would like to sync. The GlueSync connector listens to events produces by document changes inside this bucket, and processes them replicating the data to the destination database.
The following steps are required to provide GlueSync compatibility in Couchbase Server buckets in which a Couchbase Sync Gateway instance is running into. In such case, the events produced by Couchbase document changes must be temporarily stored in a secondary bucket and then brought back to the Data bucket. This avoids a problematic condition called interbucket recursion.
The user is required to create a secondary bucket, named for the sake of example “Helper bucket”, in order to allow the custom Eventing functions to operate correctly.
In order to activate this feature you should enable it in the GlueSync config file setting the
isSyncGatewayPresent variable to