{"id":9770,"date":"2021-08-13T00:00:35","date_gmt":"2021-08-13T07:00:35","guid":{"rendered":"https:\/\/www.couchbase.com\/blog\/?p=9770"},"modified":"2025-06-13T17:21:06","modified_gmt":"2025-06-14T00:21:06","slug":"collections-simplify-your-analysis-with-couchbase-analytics","status":"publish","type":"post","link":"https:\/\/www.couchbase.com\/blog\/collections-simplify-your-analysis-with-couchbase-analytics\/","title":{"rendered":"Simplify Your Data Analysis with Scopes & Collections in Couchbase Analytics"},"content":{"rendered":"

Scopes and Collections aren’t just for organizing your data<\/strong> \u2013 now they can be used for your data analytics as well. <\/p>\n

As part of the Couchbase 7.0 release<\/a>, support for Scopes and Collections has been extended to the Analytics Service as well. <\/p>\n

Scopes and Collections are logical containers<\/a> within a Couchbase Bucket. A Collection is a data container within a Bucket. A Scope is a mechanism for grouping multiple Collections within a Bucket. Collections allow users to group related data \u2013 much like tables in relational databases. <\/p>\n

Let’s take a closer look at how your team can use Scopes and Collections as part of your enterprise data analysis. But first, let’s clarify some terminology.<\/p>\n

Collections Terminology in Couchbase 7.0<\/h2>\n

The Couchbase Analytics Service<\/a> includes the following key concepts that are used in the 6.x and 7.0 releases:<\/p>\n

Dataverses<\/a>:<\/strong> Dataverse is short for data universe, a top-level organizing concept and a namespace for other metadata entities (such as links, Buckets, datasets, indexes, etc). There is one Default dataverse already created (and it can’t be deleted).<\/p>\n

Datasets<\/a>:<\/strong> Datasets are containers that hold JSON objects linked to underlying Collections. As you can imagine, the new Collections feature fits well with Analytics datasets. In fact, datasets are synonymous with Collections.<\/p>\n

How Collections Work in Couchbase Analytics<\/h2>\n

Before digging into how Collections work in Couchbase Analytics, let\u2019s take a step back and look at how Collections work in the Data Service. <\/p>\n

Consider a travel industry dataset that involves airline and hotel bookings. Let’s say we have a Bucket named `travel`. A Bucket is the equivalent of a database in the relational model. Within that `travel` Bucket, we have a Scope called `inventory` (similar to a schema in RDBMS) and within that `inventory` Scope, we have four Collections: `airlines`, `airports`, `routes` and `hotels` (these would be tables in RDBMS). <\/p>\n

I’ve illustrated this example in Diagram A below:<\/p>\n

<\/div>\n

\"Bucket,<\/a><\/p>\n

<\/div>\n

Next up, Diagram B below shows how Collections in the Data Service appear in the Analytics Service:<\/p>\n

<\/div>\n

\"How<\/a><\/p>\n

<\/div>\n

There are multiple ways to use your Collections with the Couchbase Analytics Service. In our example, let’s say we want to enable the Hotel Collection. In the Analytics workbench, we have a few options using these Analytics Data Definition Languages (DDLs):<\/p>\n

    \n
  1. If you’re familiar with the Analytics Service, leverage any of the following statements (supported in 6.x and 7.0) to create the Hotel Collection from above:\n