Destinations
Couchbase
Send processed data from Unstructured to Couchbase.
The requirements are as follows.
- For the Unstructured Platform, only Couchbase Capella clusters are supported.
- For Unstructured Ingest, Couchbase Capella clusters and local Couchbase server deployments are supported.
For Couchbase Capella, you will need:
-
A Couchbase Capella account. Create an account.
-
A Couchbase Capella cluster. Create a cluster.
-
A cluster connection string. Learn how.
-
A username and password. Learn how.
-
Incoming IP address allowance. Learn how.
To get Unstructured’s IP address ranges, go to https://assets.p6m.u10d.net/publicitems/ip-prefixes.json and allow all of the
ip_prefix
fields’ values that are listed.These IP address ranges are subject to change. You can always find the latest ones in the preceding file.
For a local Couchbase server, you will need:
- Installation of a local Couchbase server. Learn how.
- Connection details to the local Couchbase server. Learn how.
To learn more about how to set up a Couchbase cluster and play with data, refer to this tutorial.
To create the destination connector:
- On the sidebar, click Connectors.
- Click Destinations.
- Cick New or Create Connector.
- Give the connector some unique Name.
- In the Provider area, click Couchbase.
- Click Continue.
- Follow the on-screen instructions to fill in the fields as described later on this page.
- Click Save and Test.
Fill in the following fields:
- Name (required): A unique name for this connector.
- Bucket (required): The name of the bucket to connect to on the cluster.
- Connection string (required): The connection string for the Couchbase cluster.
- Scope: The name of the scope in the bucket. The default is
_default
if not otherwise specified. - Collection: The name of the collection in the scope. The default is
_default
if not otherwise specified. - Batch Size: The maximum number of documents per transmitted batch. The default is
50
if not otherwise specified. - Collection ID key (source connector only): The name of the collection field that contains the document ID. The default is
id
if not otherwise specified - Username (required): The cluster access name (username) that has access to the cluster.
- Password (required): The password for the corresponding username.
Was this page helpful?