DeltaForge ODBC Driver 1.0.8

What's Changed

Compute routing and usage attribution for the DeltaForge ODBC driver.

• The driver now sends a compute-node selector header on every query. When you have pinned or pre-selected a compute node, the request targets that node directly (direct-dial); when no node is selected, the server side picks one and load-balances across the pool. The same driver works uniformly against a single node or a routed compute fleet.
• The driver now tags its requests as an ODBC client, so DeltaForge's per-table and fleet usage dashboards record when the data lake was reached through ODBC (Power BI, Excel, Tableau, DBeaver, and other ODBC tools).
• Aligned to the 1.0.8 platform release.

Result handling, type mapping, and SQLGetData behaviour are unchanged from 1.0.610; this release adds the two new request headers above and nothing else on the wire.

DeltaForge ODBC Driver 1.0.610

What's Changed

Windows installer hardening for the DeltaForge ODBC driver.

• The Authenticode-signed MSI now bundles the full set of runtime dependencies (Apache Arrow, libcurl, and the compression and codec libraries) next to the driver, so the registered driver loads on a clean machine with no extra prerequisites.
• The bundled Power BI Power Query connector (DeltaForgeOdbc.mez) is installed into the Power BI Desktop Custom Connectors folder on install, following OneDrive Known Folder Redirection.

This is a Windows-packaging fix on top of the 1.0.6 engine; the driver behaviour is unchanged.