Actions35
- Genie Actions
- Databricks SQL Actions
- Unity Catalog Actions
- Model Serving Actions
- Files Actions
- Vector Search Actions
Overview
The "Get Index" operation within the Vector Search resource of this Databricks node allows users to retrieve metadata or details about a specific vector search index by its name. This is useful in scenarios where you want to verify the existence, configuration, or status of an index before performing further operations such as querying or updating it.
Practical examples include:
- Checking if a vector search index exists before inserting new data.
- Retrieving index details to understand its schema or settings.
- Validating index readiness for query operations.
Properties
| Name | Meaning |
|---|---|
| Index Name | Name of the vector search index |
Output
The output JSON will contain the details of the requested vector search index. This typically includes metadata such as the index's configuration, status, creation time, and other relevant attributes describing the index. The exact structure depends on the Databricks API response for the get index endpoint.
If the node supports binary data output (not indicated here), it would represent any associated binary content related to the index, but this is unlikely for a get index operation.
Dependencies
- Requires an active connection to Databricks with appropriate API credentials (an API key or token).
- The node uses the Databricks API endpoint configured via the host URL and authorization token provided in the credentials.
- No additional external services are required beyond Databricks itself.
Troubleshooting
Common issues:
- Invalid or missing index name: The node requires a valid index name; ensure the "Index Name" property is correctly set.
- Authentication errors: Verify that the API token and host URL in the credentials are correct and have sufficient permissions.
- Network or connectivity problems: Ensure the n8n instance can reach the Databricks API endpoint.
Common error messages:
- 404 Not Found: The specified index does not exist. Double-check the index name.
- 401 Unauthorized: Authentication failed. Check API token validity.
- 400 Bad Request: Input parameters may be invalid or malformed.
Resolving these usually involves verifying input parameters, credentials, and network access.
Links and References
- Databricks Vector Search API Documentation (generic link, replace with actual if available)
- n8n Documentation on Creating Custom Nodes