HDInsight Interactive Query Python API Docs | dltHub
Build a HDInsight Interactive Query-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
HDInsight Interactive Query provides a REST API to submit and manage Hive queries within Azure HDInsight clusters. The REST API base URL is https://CLUSTERNAME.azurehdinsight.net/api/v1/clusters/CLUSTERNAME and all requests require a Bearer token in the Authorization header.
dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv pip install "dlt[workspace]" and start loading HDInsight Interactive Query data in under 10 minutes.
What data can I load from HDInsight Interactive Query?
Here are some of the endpoints you can load from HDInsight Interactive Query:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| cluster_status | /templeton/v1/status | GET | Returns the status of the WebHCat server. | |
| hive_version | /templeton/v1/version/hive | GET | Returns the version of Hive installed on the cluster. | |
| job_status | /templeton/v1/jobs/{jobid} | GET | .status | Returns the status of a specific job by ID. |
| mapreduce_jobs | /templeton/v1/mapreduce/jar | POST | Submits a MapReduce jar job. | |
| hive_query | /hive2 | POST | Gateway endpoint for submitting Hive queries (via HiveServer2). |
How do I authenticate with the HDInsight Interactive Query API?
Requests require an Authorization header with a Bearer token acquired via Microsoft Entra ID (OAuth 2.0). Some operations may also require an X-Requested-By header.
1. Get your credentials
HDInsight clusters typically use one of two authentication methods: basic authentication or Entra ID OAuth 2.0. For basic authentication, use the cluster admin username and password defined during cluster creation. To obtain Entra ID bearer tokens, register an application in the Azure portal, grant it appropriate cluster access, and perform a client_credentials flow request to https://login.microsoftonline.com/{tenant_id}/oauth2/v2.0/token. Alternatively, you can programmatically retrieve gateway settings (containing credentials) using the Azure Management API: POST to https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HDInsight/clusters/{clusterName}/getGatewaySettings?api-version={api-version}.
2. Add them to .dlt/secrets.toml
[sources.hdinsight_interactive_query_source] username = "admin" password = "your_cluster_password" cluster_name = "your_cluster_name" # If using Entra ID OAuth 2.0 # client_id = "your_app_id" # client_secret = "your_app_secret" # tenant_id = "your_tenant_id"
dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.
How do I set up and run the pipeline?
Set up a virtual environment and install dlt:
uv venv && source .venv/bin/activate uv pip install "dlt[workspace]"
1. Install the dlt AI harness:
dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex
This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →
2. Install the rest-api-pipeline toolkit:
dlthub ai toolkit rest-api-pipeline install
This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →
3. Start LLM-assisted coding:
Use /find-source to load data from the HDInsight Interactive Query API into DuckDB.
The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.
4. Run the pipeline:
python hdinsight_interactive_query_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline hdinsight_interactive_query_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset hdinsight_interactive_query_data The duckdb destination used duckdb:/hdinsight_interactive_query.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline hdinsight_interactive_query_pipeline show
This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.
Python pipeline example
This example loads templeton and api from the HDInsight Interactive Query API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def hdinsight_interactive_query_source(token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://CLUSTERNAME.azurehdinsight.net/api/v1/clusters/CLUSTERNAME", "auth": {"type": "bearer", "token": token}, }, "resources": [ {"name": "cluster_status", "endpoint": {"path": "templeton/v1/status"}}, {"name": "hive_version", "endpoint": {"path": "templeton/v1/version/hive"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="hdinsight_interactive_query_pipeline", destination="duckdb", dataset_name="hdinsight_interactive_query_data", ) load_info = pipeline.run(hdinsight_interactive_query_source()) print(load_info)
To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.
How do I query the loaded data?
Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("hdinsight_interactive_query_pipeline").dataset() sessions_df = data.cluster_status.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM hdinsight_interactive_query_data.cluster_status LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("hdinsight_interactive_query_pipeline").dataset() data.cluster_status.df().head()
See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.
What destinations can I load HDInsight Interactive Query data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example value |
|---|---|
| DuckDB (local, default) | "duckdb" |
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI harness:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-platform— Deploy, schedule, and monitor your pipeline in production.
dlthub ai toolkit data-exploration install dlthub ai toolkit dlthub-platform install
Was this page helpful?
Community Hub
Need more dlt context for HDInsight Interactive Query?
Request dlt skills, commands, AGENT.md files, and AI-native context.