September 2026 Summaries

A PyDough-based analytics pipeline was evaluated on dbt Labs’ 11-question ACME Insurance benchmark, using 20 independent runs per question and dbt’s comparator, and reported 100% accuracy across 220 runs, compared with dbt’s reported 98.2% for its modeled Semantic Layer and 64.5% for raw-schema text-to-SQL. Because dbt’s original execution environment could not be reproduced locally, the evaluation used a SQLite database reconstructed from the published DDL and seed data, including recovery of a relationship absent from the DDL. Rather than having an LLM generate SQL and reconstruct joins for each request, the system profiles schema and data, uses limited LLM-assisted column descriptions, stores the resulting context in a PyDough metadata graph, and generates a higher-level PyDough query that is compiled into SQL. The approach aims to reduce join, dialect, and silent-error risks by defining relationships centrally, validating graph traversals at compile time, and using multiple candidate queries with result-based consensus or a judging step when outputs differ. The authors argue that the results support dbt’s conclusion that raw DDL alone is insufficient for dependable AI analytics while suggesting that semantic context can be substantially derived from schemas and data rather than exclusively hand-modeled.

BodoSQL relies on a customized version of Apache Calcite to transform SQL queries into optimized physical plans for its C++ analytics backend. Calcite supplies the parser, validator, SQL-to-relational-algebra converter, schemas, and optimization framework, while BodoSQL extends these components to support Snowflake-style syntax and semantics, external catalog metadata, custom relational nodes, and specialized query behavior. Queries progress from a SQL abstract syntax tree through validation and logical relational planning before optimization combines Calcite’s rule-based HEP planner for transformations such as filter pushdown with its cost-based Volcano planner for selecting efficient join orders and physical operators. BodoSQL then applies additional physical-plan optimizations, including subplan caching and runtime join filters, to reduce redundant work and data processing. Although many adaptations use Calcite’s public extension points, some require modifying internal Calcite code; BodoSQL manages these changes through duplicated source files, Maven Shade replacements, annotations, and manual reconciliation during upstream upgrades to limit maintenance overhead.