Astra DB
If you’re new to Unstructured, read this note first.
Before you can create a destination connector, you must first sign up for Unstructured and get your Unstructured API key. After you sign up, the Unstructured user interface (UI) appears, which you use to get the key. To learn how, watch this 40-second how-to video.
After you create the destination connector, add it along with a source connector to a workflow. Then run the worklow as a job. To learn how, try out the hands-on Workflow Endpoint quickstart, go directly to the quickstart notebook, or watch the two 4-minute video tutorials for the Unstructured Python SDK.
You can also create destination connectors with the Unstructured user interface (UI). Learn how.
If you need help, reach out to the community on Slack, or contact us directly.
You are now ready to start creating a destination connector! Keep reading to learn how.
Send processed data from Unstructured to Astra DB.
The requirements are as follows.
- An Astra account. Create or sign in to an Astra account.
- A database in the Astra account. Create a database in an account.
- An application token for the database. Create a database application token.
- A namespace in the database. Create a namespace in a database.
- A collection in the namespace. Create a collection in a namespace.
To create an Astra DB destination connector, see the following examples.
Replace the preceding placeholders as follows:
<name>
(required) - A unique name for this connector.<token>
(required) - The application token for the database.<api-endpoint>
(required) - The database’s associated API endpoint.<collection-name>
(required) - The name of the collection in the namespace.<keyspace>
- The name of the keyspace in the collection. The default isdefault_keyspace
if not otherwise specified.<batch-size>
- The maximum number of records to send per batch. The default is20
if not otherwise specified.flatten_metadata
- Set totrue
to flatten the metadata into each record. Specifically, when flattened, the metadata key values are brought to the top level of the element, and themetadata
key itself is removed. By default, the metadata is not flattened (false
).
Was this page helpful?