This article gives an overview of the available blocks in the Databricks connector in Qlik Application Automation. It will also go over a basic example of triggering a model transition and catching the information using a webhook for alerting purposes.
Databricks is a cloud-based collaborative data science, data engineering, and data analytics platform that combines the best of data warehouses and data lakes into a lakehouse architecture.
This connector consists of:
For authenticating, you will need to provide an API Token. To get an API Token: click on Settings in the lower left corner of your Databricks workspace, then click User Settings, then go to the Access Tokens tab, then click the Generate New Token button.
Let's now go over a basic example of how to trigger a model transition and how to catch this information using a webhook using the Databricks connector.
For this use case, we will need two automations. The first one will serve to trigger the model transition, and the second one will have a webhook configured for the same model, to trigger when a transition is created. We will use the Slack connector for alerting.
Steps to configure the first automation:
Steps to configure the second automation:
Now, by running the first automation, you will create and approve a model transition. If you check the second automation, you will notice that it was automatically triggered and the Slack message containing the transition information was sent.
The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.