Databricks icon

Databricks

Interact with Databricks API
Join our community

Actions42

Overview

This node interacts with the Databricks Genie API to retrieve query results from a specific message attachment within a conversation in a Genie space. It is useful when you want to programmatically fetch the results of a query that was executed as part of a message attachment in a collaborative environment managed by Databricks Genie.

Typical use cases include:

  • Automating retrieval of query results after executing queries in conversations.
  • Integrating query result fetching into workflows for further processing or reporting.
  • Monitoring and extracting data from conversations without manual intervention.

For example, after running a query attached to a message in a Genie conversation, this node can be used to fetch the resulting dataset for analysis or storage.

Properties

Name Meaning
Space ID The unique identifier of the Genie space where the conversation resides.
Conversation ID The unique identifier of the conversation containing the message.
Message ID The unique identifier of the message that holds the attachment with the query results.
Attachment ID The unique identifier of the message attachment which contains the query result to fetch.

Output

The node outputs a JSON object representing the response from the Genie API endpoint for query results. This typically includes the data returned by the executed query associated with the specified message attachment.

The structure of the output JSON depends on the query result format provided by the Genie API but generally contains fields such as rows of data, metadata about the query execution, and status information.

No binary data output is produced by this operation.

Dependencies

  • Requires an API authentication token credential for Databricks (an API key or token).
  • Needs the base URL of the Databricks instance configured in the node credentials.
  • The node makes HTTP requests to the Genie API endpoints under the authenticated context.

Troubleshooting

  • Common issues:

    • Invalid or expired API token leading to authentication errors.
    • Incorrect Space ID, Conversation ID, Message ID, or Attachment ID causing "not found" errors.
    • Network connectivity problems preventing API calls.

  • Error messages:

    • API Error: <status code> <status text>: Indicates the API responded with an error status. Check IDs and permissions.
    • Network Error: No response received from server: Suggests network issues or incorrect base URL.
    • Other errors are logged with details; enabling continue-on-fail allows workflow continuation despite errors.

  • Resolutions:

    • Verify all IDs are correct and exist in the target Databricks Genie environment.
    • Ensure the API token is valid and has sufficient permissions.
    • Confirm network access to the Databricks host URL.
    • Use the node's logging to inspect request and response details for debugging.

Links and References

Discussion