Please use the form below to provide your feedback. Because your feedback is valuable to us, the information you submit in this form is recorded in our issue tracking system (JIRA), which is publicly available. You can track the status of your feedback using the ticket number displayed in the dialog once you submit the form.

Google Cloud Storage (GCS)

  • Capella Analytics
  • how-to
    +
    To provide query access to OLAP data in GCS, you create an external link and associate it with an external collection.

    Google Cloud Storage (GCS) external sources allow you to connect to and query data stored in GCS buckets directly from your database. Before setting up a GCS external source, make sure you have the necessary GCP permissions and configured credentials.

    You also need the following information about the GCS bucket containing the data you want to query:

    Credentials

    To create an external link for private data in a GCS bucket, you must supply the JSON credentials of the service account that has access to the GCS bucket.

    Use the service account key to sign a JSON Web Token (JWT) and exchange it for an access token. Because service account keys are a security risk if not managed correctly, you should choose a more secure alternative to service account keys whenever possible.

    These credentials must have permission to list and read data from GCS bucket. For more information, see Service accounts overview in the Google Cloud documentation.

    You do not need credentials for publicly available data in a GCS bucket.

    When you create an external link, be sure to follow best practices for security. Couchbase recommends that you grant the minimum possible permissions to perform the required operations, and allow access only to the required data and resources. You should never use root account credentials.

    The Location Path

    When you create an external collection based on a GCS bucket, you can supply a path to the files Capella Analytics queries. A path consists of one or more prefixes that define a hierarchical organization, using a format such as topLevel/nextLevel/lowestLevel. The path does not include filenames.

    If you use the GCS bucket console, prefixes are also referred to as folders.

    To make querying the external data source as efficient as possible, you should supply a path that’s as specific and precise as possible. You can use static prefixes, dynamic prefixes, or a mixture of both to define a path. For information about static and dynamic prefixes, see Design a Location Path.

    Because you cannot index the data located in an external store, Couchbase encourages thoughtful design of the paths used in external collections.

    For information about using prefixes for data on a GCS bucket, see List the objects in a bucket using a prefix filter in the Google Cloud documentation.

    You can select a subset of the files in a location by using fields that include and exclude filenames.

    For detailed instructions on setting up and configuring Google Cloud Storage external sources, see the following:

    See Also