ArchitectureA supervised JVM-class runtime — OLTP on seven engines, OLAP on three. AI-native, MCP-native, observable as plain SQL.Read the architecture
Está viendo la edición Perú. Está viendo la edición Colombia. You're viewing the Pakistan edition. Cambiar a la edición global →Cambiar a la edición global →Switch to the global edition →
Data and enginesProduct Release1 min read

Google BigQuery as a JDBC engine, with its driver fetched on first use

A complete driver on the Simba JDBC connector: dialects, types, metadata and constraints across 37 files. The connector is downloaded as a bundle and extracted on first use; BigQuery joins the engine list.

BigQuery had been reachable as a vector and OLAP store through the AI surface. This release makes it a database engine like the others, with a driver the platform fetches itself.

The driver

  • Complete Dialects, types, metadata and constraints on the Simba JDBC 4.2 connector, in 37 files and about 3,000 lines.
  • Fetched on first use The connector is downloaded as a bundle, extracted by the artifact loader, and the archive deleted after extraction.
  • Registered BigQuery joins the engine type names and labels, with a test pool factory.

What stayed out

  • Procedures A procedural dialect was attempted and withdrawn a week later: BigQuery lacks the callable-statement protocol, so functions ran through SELECT, and the mismatch was judged not worth carrying. BigQuery is a query and load target, not a home for procedures.

An engine that is honest about what it does not do is easier to recommend than one that pretends. This one queries.

On the platformAnalytics & ReportingPlatform

All posts