DeltaForge ADBC Driver 1.0.8

What's Changed

Compute-pool routing and usage attribution for the DeltaForge ADBC driver.

• The Arrow-native driver now participates in DeltaForge's compute routing. Every query carries an x-deltaforge-node selector: when you have pinned a compute node the request goes straight to it (direct-dial), and when no node is selected the server picks one for you (load-balancing). The driver behaves the same whether you point it at a single node or a routed compute pool.
• Requests are tagged as ADBC traffic (X-DeltaForge-Client: adbc), so DeltaForge's per-table and fleet usage dashboards record when your data lake was reached through the ADBC driver.
• Versioned to the 1.0.8 platform release.

These are two new outbound request headers; Arrow result handling, type mapping, and schema are unchanged from 1.0.610.

DeltaForge ADBC Driver 1.0.610

What's Changed

Windows installer hardening for the DeltaForge ADBC driver.

• The Authenticode-signed MSI now bundles the full set of runtime dependencies (Apache Arrow, Parquet, libcurl, OpenSSL, and the compression and codec libraries) next to the driver, so it loads on a clean machine with no extra prerequisites.
• The bundled Power BI Power Query connector (DeltaForgeAdbc.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.