Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Copy/Move data from _default scope to 'development' scope on adb-cb1 #396

Open
gopa-noaa opened this issue Jul 31, 2024 · 2 comments
Open
Assignees
Labels
couchbase task Tasks break a project down into discrete steps VXingest issues related to the VXingest project

Comments

@gopa-noaa
Copy link
Contributor

Now that we have the new Couchbase 7.6 version working, we should come up with a plan on how to move data to the newly created 'development' scope. This only needs to be done on adb-cb1, since once data is in adb-cb1, XDCR will take take of replicating the data to the 3-node cluster. Please note that once data is in the development scope, we need to update code to point to the new scope, there are three related issues that address this, one each for ingest, metadata update and MATS.

@gopa-noaa
Copy link
Contributor Author

https://docs.couchbase.com/server/current/manage/manage-xdcr/replicate-using-scopes-and-collections.html#replicate-data-between-collections-explicitly-with-the-ui
This below is important:
Delete the existing replication: this is because we now intend to create another replication to the same bucket, ts; and XDCR only permits one replication to be defined, for a given target-bucket.
So tis means deleting our current replication to On Prem 3-node cluster temporarily.

@gopa-noaa
Copy link
Contributor Author

BTW, looks like we can replicate from any cluster.collection to any other cluster.collection by specifying the following rule in XDCR

{_default.METAR:development.METAR}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
couchbase task Tasks break a project down into discrete steps VXingest issues related to the VXingest project
Projects
None yet
Development

No branches or pull requests

2 participants