Databricks Export

Last updated:

What does the Databricks Export app do?

The Databricks Export app for PostHog will push data from PostHog to Databricks, once every minute. The app creates a table and migrates data from DBFS to a database.

What are the requirements for this app?

Using this app requires either PostHog Cloud, or a self-hosted PostHog instance running version 1.30.0 or later.

Not running 1.30.0? Find out how to update your self-hosted PostHog deployment!

How do I install the Databricks Export app for PostHog?

  1. Visit the 'Apps' page in your instance of PostHog.
  2. Search for 'Databricks' and select the app, press Install.
  3. Follow the steps below to configure the app.

Configuration

You will need the following, in order to full configure this app:

You will also need to give a temporary filename path for saving raw data, and a database name for where you want to store the data. Enter events in comma ( , ) separated way in order to ignore the data.

OptionDescription
Domain Name
Type: string
Required: True
Domain name of your databrics cloud instance
API Key
Type: string
Required: True
API key of your databrics cloud instance
File Name
Type: string
Required: True
Default filename for the csv file
Python Support File Upload
Type: string
Required: True
Default filename for python job file
Cluster Id
Type: string
Required: True
Get cluster details from the databricks portal
Database Name
Type: string
Required: True
Database name to store the data
Events to Ignore
Type: string
Required: False
Events to ignore

What are the limitations for this app?

The Databricks Export app cannot currently sync historic data, or change the frequency with which it pushes data to PostHog.

Interesting in contributing to the app to remove these limitations? Check the GitHub repo!

Is the source code for this app available?

PostHog is open-source and so are all apps on the platform. The source code for the Databricks Export app is available on GitHub.

Who created this app?

We'd like to thank community members Sandeep Guptan and Himanshu Garg for their work creating this app. Thank you, both!

Who maintains this app?

This app is maintained by the community. If you have issues with the app not functioning as intended, please raise a bug report to let us know!

Where can I find out more?

Check Databricks' API documentation for more information on pulling and pushing data from/to Databricks.

What if I have feedback on this app?

We love feature requests and feedback! Please create an issue to tell us what you think.

What if my question isn't answered above?

We love answering questions. Ask us anything via our Support page.

You can also join the PostHog Community Slack group to collaborate with others and get advice on developing your own PostHog apps.

Questions?

Was this page useful?

Next article

Engage Connector

What does the Engage Connector do? This app connects PostHog to Engage , a marketing automation platform, and sends data to Engage for use in segmentation, targeting and automation. Specifically, this app only exports your Custom and $identify events to Engage. Extra event properties and metadata are also processed and sent to Engage. The example above, using the PostHog JS SDK, appends extra properties to the identify event. These extra properties are also sent to Engage. What are the…

Read next article