Destination connectors
Vectara
This page was recently updated. What do you think about it? Let us know!.
Batch process all your records to store structured outputs in Vectara.
The requirements are as follows.
- A Vectara account.
- The customer ID for the account.
- The name and key for the target corpus in the account.
- The OAuth authentication URL, client ID, and client secret for accessing the target corpus.
The Vectara connector dependencies.
You might also need to install additional dependencies, depending on your needs. Learn more.
The following environment variables:
VECTARA_CUSTOMER_ID
- The customer ID for the target Vectara account, represented by--customer-id
(CLI) orcustomer_id
(Python).VECTARA_CORPUS_NAME
- The name of the target corpus in the account, represented by--corpus-name
(CLI) orcorpus_name
(Python).VECTARA_CORPUS_KEY
- The name of the corpus’s key, represented by--corpus-key
(CLI) orcorpus_key
(Python).VECTARA_OAUTH_TOKEN_URL
- The OAuth token URL for getting and refreshing OAuth access tokens in the account, represented by--token-url
(CLI) ortoken_url
(Python).VECTARA_OAUTH_CLIENT_ID
- A valid OAuth client ID in the account, represented by--oauth-client-id
(CLI) oroauth_client_id
(Python).VECTARA_OAUTH_CLIENT_SECRET
- The OAuth client secret for the client ID, represented by--oauth-client-secret
(CLI) oroauth_client_secret
(Python).
These environment variables:
UNSTRUCTURED_API_KEY
- Your Unstructured API key value.UNSTRUCTURED_API_URL
- Your Unstructured API URL.
Now call the Unstructured CLI or Python SDK. The source connector can be any of the ones supported.
This example uses the local source connector: