Skip to content

Latest commit

 

History

History
39 lines (29 loc) · 3.33 KB

README.md

File metadata and controls

39 lines (29 loc) · 3.33 KB

databricks-sql-connector Example Usage

We provide example scripts so you can see the connector in action for basic usage. You need a Databricks account to run them. The scripts expect to find your Databricks account credentials in these environment variables:

- DATABRICKS_SERVER_HOSTNAME
- DATABRICKS_HTTP_PATH
- DATABRICKS_TOKEN

Follow the quick start in our README to install databricks-sql-connector and see how to find the hostname, http path, and access token. Note that for the OAuth examples below a personal access token is not needed.

How to run an example script

To run all of these examples you can clone the entire repository to your disk. Or you can use curl to fetch an individual script.

Clone the repo

  1. Clone this repository to your local system
  2. Follow the quick start in the README to install the connector and obtain authentication credentials.
  3. cd examples/
  4. Then run any script using the python CLI. For example python query_execute.py

Fetch with curl

  1. Follow the quick start in the README to install the connector and obtain authentication credentials.
  2. Use the GitHub UI to find the URL to the Raw version of one of these examples. For example: https://raw.githubusercontent.com/databricks/databricks-sql-python/main/examples/query_execute.py
  3. curl this URL to your local file-system: curl https://raw.githubusercontent.com/databricks/databricks-sql-python/main/examples/query_execute.py > query_execute.py
  4. Then run the script with the python CLI. python query_execute.py

Table of Contents

  • query_execute.py connects to the samples database of your default catalog, runs a small query, and prints the result to screen.
  • insert_data.py adds a tables called squares to your default catalog and inserts one hundred rows of example data. Then it fetches this data and prints it to the screen.
  • query_cancel.py shows how to cancel a query assuming that you can access the Cursor executing that query from a different thread. This is necessary because databricks-sql-connector does not yet implement an asynchronous API; calling .execute() blocks the current thread until execution completes. Therefore, the connector can't cancel queries from the same thread where they began.
  • interactive_oauth.py shows the simplest example of authenticating by OAuth (no need for a PAT generated in the DBSQL UI) while Bring Your Own IDP is in public preview. When you run the script it will open a browser window so you can authenticate. Afterward, the script fetches some sample data from Databricks and prints it to the screen. For this script, the OAuth token is not persisted which means you need to authenticate every time you run the script.
  • persistent_oauth.py shows a more advanced example of authenticating by OAuth while Bring Your Own IDP is in public preview. In this case, it shows how to use a sublcass of OAuthPersistence to reuse an OAuth token across script executions.
  • set_user_agent.py shows how to customize the user agent header used for Thrift commands. In this example the string ExamplePartnerTag will be added to the the user agent on every request.
  • staging_ingestion.py shows how the connector handles Databricks' experimental staging ingestion commands GET, PUT, and REMOVE.