-
Notifications
You must be signed in to change notification settings - Fork 0
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
Re-structure Capella Bucket=>Scope=>Collection configuration #379
Comments
It implies that the metadata is moved from METAR collection to COMMON
collection and that METAR collection will only have type "DD" documents
(the same for RAOB collection). This will require code changes to ingest,
metadata scripts, and client.
randy
…On Wed, May 29, 2024 at 11:06 AM Gopa ***@***.***> wrote:
No change to bucket, 3 scopes , development, integration, production, and
2 scopes under each, currently just METAR and COMMON.
—
Reply to this email directly, view it on GitHub
<#379>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGDVQPSO6P5YDQA2D2J6CNDZEYDJBAVCNFSM6AAAAABIPLDB3CVHI2DSMVQWIX3LMV43ASLTON2WKOZSGMZDGOBRGY4DQOI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--
Randy Pierce
|
From a quick Google-ing a scope cannot be renamed after it is created. Have sent email to Couchbase ...
|
A couple of other questions:
|
To summarize the discussion from the dev meeting: We decided we need to move this issue up and address how best to use collections, scopes, and buckets for our project & application. We would like to come up with some use cases & whiteboard through how key parts of the application lifecycle would work with different data models. Ideally this would happen during the ingest meeting. During the meeting we
Information needed
ContextCouchbase Server 7 (released in 2021) introduced Scopes & Collections. Previously it was recommended to put all data in a “Bucket” and distinguish the documents with a |
This link explains Collections and Scope: Just noting down some salient points below: A collection is a data container. A scope is a mechanism for the grouping of multiple collections. Up to 1000 scopes can be created per cluster. Benefits of Scopes and Collections The logical grouping of similar documents; potentially simplifying operations such as query, XDCR, and backup and restore. The increased efficiency of indexing, due to the Data Service being able to provide documents from specific collections to the Index Service. Simplified querying, since query statements are able to easily specify particular subsets of documents. Easier migration from relational databases to Couchbase Server, since collections can be designed to correspond to pre-existing relational tables. Secure isolation of different document-types, within a bucket; allowing applications to be specifically authorized to use only their appropriate subsets of data (see Access to Scopes and Collections, below). This should help give us some guidance in organizing our document hierarchy. Lets plan to discuss further. |
Thanks, Gopa! That makes it sound like it would be beneficial to explore using collections more. 2. How do collections, scopes, and buckets interact with XDCR & Time-To-Live fields?TTL fields
XDCR
|
No change to bucket, 3 scopes , development, integration, production, and 3 collections under each, currently just METAR, RAOB, and COMMON.
The text was updated successfully, but these errors were encountered: