Duaer

Integrations

Use Databricks Vector Store in Duaer

In Duaer, Databricks Vector Store is an AI root node. It takes Embedding, Document, and Reranker sub-nodes. Its modes are Get Many, Insert Documents, Retrieve Documents (As Vector Store for Chain/Tool), and Retrieve Documents (As Tool for AI Agent).

Add Databricks Vector Store to a Duaer digital organization

  1. On the Duaer canvas, open the node panel, search for Databricks Vector Store, and connect it after the previous node.
  2. Connect the sub-nodes it needs to the inputs under Databricks Vector Store (Embedding, Document, and Reranker), starting with an Embedding.
  3. In Credential to connect with, pick or create a Databricks OAuth2 API credential.
  4. Pick an Operation Mode: Get Many, Insert Documents, Retrieve Documents (As Vector Store for Chain/Tool), or Retrieve Documents (As Tool for AI Agent).
  5. Set Index.
  6. If needed, select Add Option for the optional settings listed below.
  7. Select Execute step and check the output.

Databricks Vector Store modes in Duaer

  • Get Many: Get many ranked documents from vector store for query.
  • Insert Documents: Insert documents into vector store.
  • Retrieve Documents (As Vector Store for Chain/Tool): Retrieve documents from vector store to be used as vector store with AI nodes.
  • Retrieve Documents (As Tool for AI Agent): Retrieve documents from vector store to be used as tool with AI nodes.

Databricks Vector Store options in Duaer

Under Add Option, Databricks Vector Store offers Metadata Columns, Search Mode, and Metadata Filter.

Sub-nodes Databricks Vector Store takes in Duaer

Connect sub-nodes to the inputs under Databricks Vector Store: Embedding, Document, and Reranker. Each sub-node keeps its own credential and settings.

Questions

What do you set on Databricks Vector Store in Duaer?

In Duaer, Databricks Vector Store mainly takes Index and Content Column.

Which credential does Databricks Vector Store use in Duaer?

Duaer's Databricks Vector Store uses a Databricks OAuth2 API credential. The secret stays in the credential, not in node parameters.

In this section