Databricks SQL Connector for Python
The Databricks SQL Connector for Python allows you to develop Python applications that connect to Databricks clusters and SQL warehouses. It is a Thrift-based client with no dependencies on ODBC or JDBC. It conforms to the Python DB API 2.0 specification.
This connector uses Arrow as the data-exchange format, and supports APIs (e.g. fetchmany_arrow) to directly fetch Arrow tables. Arrow tables are wrapped in the ArrowQueue class to provide a natural API to get several rows at a time. PyArrow is required to enable this and use these APIs, you can install it via pip install pyarrow or pip install databricks-sql-connector[pyarrow].
The connector includes built-in support for HTTP/HTTPS proxy servers with multiple authentication methods including basic authentication and Kerberos/Negotiate authentication. See docs/proxy.md and examples/proxy_authentication.py for details.
You are welcome to file an issue here for general use cases. You can also contact Databricks Support here.
Requirements
Python 3.9 or above is required.
Documentation
For the latest documentation, see
For a full reference of every sql.connect(...) keyword argument — type,
default, per-backend support (Thrift vs Kernel), and meaning — see
CONNECTION_PARAMETERS.md.
Quickstart
Installing the core library
Install using pip install databricks-sql-connector
Installing the core library with PyArrow
Install using pip install databricks-sql-connector[pyarrow]
Installing with the Rust kernel backend (use_kernel=True)
Install using pip install databricks-sql-connector[kernel]
This adds the optional databricks-sql-kernel
extension (a native Rust client core, exposed via PyO3). Pass
use_kernel=True to sql.connect(...) to route the connection through it
instead of the default Thrift backend:
connection = sql.connect(
server_hostname=host,
http_path=http_path,
access_token=token,
use_kernel=True,
)
Notes:
- Requires Python >= 3.10 (the kernel wheel is published as
cp310-abi3). On older interpreters the[kernel]extra installs nothing anduse_kernel=Trueraises anImportError. - The extra also pulls in PyArrow, which the kernel result path requires.
- Authentication supports PAT (
access_token), OAuth M2M/U2M, and SP-wide workload identity federation (identity_federation_client_id).
export DATABRICKS_HOST=********.databricks.com
export DATABRICKS_HTTP_PATH=/sql/1.0/endpoints/****************
Example usage:
import os
from databricks import sql
host = os.getenv("DATABRICKS_HOST")
http_path = os.getenv("DATABRICKS_HTTP_PATH")
connection = sql.connect(
server_hostname=host,
http_path=http_path)
cursor = connection.cursor()
cursor.execute('SELECT :param `p`, * FROM RANGE(10)', {"param": "foo"})
result = cursor.fetchall()
for row in result:
print(row)
cursor.close()
connection.close()
In the above example:
server-hostnameis the Databricks instance host name.http-pathis the HTTP Path either to a Databricks SQL endpoint (e.g. /sql/1.0/endpoints/1234567890abcdef), or to a Databricks Runtime interactive cluster (e.g. /sql/protocolv1/o/1234567890123456/1234-123456-slid123)
Note: This example uses Databricks OAuth U2M to authenticate the target Databricks user account and needs to open the browser for authentication. So it can only run on the user's machine.
Transaction Support
The connector supports multi-statement transactions with manual commit/rollback control. Set connection.autocommit = False to disable autocommit mode, then use connection.commit() and connection.rollback() to control transactions.
For detailed documentation, examples, and best practices, see TRANSACTIONS.md.
SQLAlchemy
Starting from databricks-sql-connector version 4.0.0 SQLAlchemy support has been extracted to a new library databricks-sqlalchemy.
- Github repository databricks-sqlalchemy github
- PyPI databricks-sqlalchemy pypi
Quick SQLAlchemy guide
Users can now choose between using the SQLAlchemy v1 or SQLAlchemy v2 dialects with the connector core
- Install the latest SQLAlchemy v1 using
pip install databricks-sqlalchemy~=1.0 - Install SQLAlchemy v2 using
pip install databricks-sqlalchemy
Contributing
See CONTRIBUTING.md
License
2 maintainers
Metadata
2 maintainers
Release files for databricks-sql-connector 4.7.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| databricks_sql_connector-4.7.0.tar.gz | 246.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| databricks_sql_connector-4.7.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 519.1 kB
Release files / databricks_sql_connector-4.7.0.tar.gz
| Download URL | databricks_sql_connector-4.7.0.tar.gz |
|---|---|
| Size | 246.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c8193aacaaf4778e468dbcb85b861c960991436db164f6f55a9eb255270ea45a
|
|
BLAKE2b-256 checksum How to use checksums |
d73a8331e95fa78ed8241090c157b7d3d75f8e86ebab77972346bfc4d0ac4ca6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / databricks_sql_connector-4.7.0-py3-none-any.whl
| Download URL | databricks_sql_connector-4.7.0-py3-none-any.whl |
|---|---|
| Size | 272.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2dedd8a5e4574dd3fac12fd6c8c1076a5d4292d7e87a9ffec5fd513253477df9
|
|
BLAKE2b-256 checksum How to use checksums |
69f49af042774fc4cb6e301913c79a512b4a0f5cc134046fb94a540c0a559ebe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for databricks-sql-connector 4.7.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
