Actions42
- Genie Actions
- Databricks SQL Actions
- Unity Catalog Actions
- Model Serving Actions
- Files Actions
- Vector Search Actions
Overview
The node interacts with the Databricks API, specifically supporting multiple resources including Vector Search. For the Vector Search - Get Index operation, it retrieves metadata or details about a specified vector search index within Databricks. This is useful when you want to verify the existence, configuration, or status of an index used for vector similarity searches.
Practical scenarios include:
- Validating that a vector search index exists before performing queries.
- Retrieving index properties to understand its configuration.
- Integrating Databricks vector search capabilities into automated workflows for data science or machine learning pipelines.
Properties
| Name | Meaning |
|---|---|
| Index Name | The name of the vector search index to retrieve information about. |
Output
The output JSON contains the response from the Databricks API about the requested vector search index. It typically includes metadata such as index configuration, status, creation time, and other relevant details describing the index.
No binary data output is involved in this operation.
Dependencies
- Requires an API authentication token credential for Databricks.
- The node uses the Databricks API endpoint configured via credentials (host URL and token).
- No additional external services are required beyond Databricks itself.
Troubleshooting
Common issues:
- Providing an incorrect or non-existent index name will likely result in an API error indicating the index was not found.
- Network connectivity problems can cause request failures.
- Invalid or expired API tokens will lead to authorization errors.
Error messages:
API Error: 404 Not Found— The specified index does not exist. Verify the index name.API Error: 401 Unauthorized— Authentication failed. Check your API token.Network Error: No response received from server— Possible network or firewall issue; ensure connectivity to Databricks.
To resolve errors, confirm the index name is correct, validate credentials, and check network access.