kosiew
e583fe9d22
## Which issue does this PR close? * Part of #20524. ## Rationale for this change The sqllogictest runner executes files in parallel, but it was hard to pinpoint which test files dominate wall-clock time. This change adds **deterministic per-file elapsed timing observability** so we can identify long-tail files and prioritize follow-up optimization work, while keeping default output usable for both local development (TTY) and CI (non-TTY). ## What changes are included in this PR? * Collect per-file elapsed durations in the sqllogictest runner and aggregate them at end-of-run. * Print a **deterministic timing summary** (stable sort: elapsed desc, path asc; stable formatting) via `MultiProgress` to avoid interleaved progress-bar noise. * Add CLI flags and environment variables to control output: * `--timing-summary auto|off|top|full` (also `SLT_TIMING_SUMMARY`) * `--timing-top-n <N>` (also `SLT_TIMING_TOP_N`, must be `>= 1`) * Default behavior: * `auto` maps to `off` for local TTY runs and `top` for CI/non-TTY runs. * Add optional debug logging for slow files (over 30s) behind `SLT_TIMING_DEBUG_SLOW_FILES=1`. * Update `datafusion/sqllogictest/README.md` with usage examples. ## Are these changes tested? * Covered by existing `sqllogictests` integration test execution; no new unit tests were added. * Manual validation plan (ran locally / in CI as applicable): * `cargo test --test sqllogictests -- push_down_filter_ --test-threads 16` * `cargo test --test sqllogictests -- --test-threads 16` * `cargo test --test sqllogictests -- --timing-summary top --timing-top-n 10` * `cargo test --test sqllogictests -- --timing-summary full` * Verified output properties: * Summary ordering is deterministic across repeated runs (elapsed desc, path asc). * `auto` mode is quiet on TTY but prints a top-N summary on non-TTY/CI. * Pass/fail behavior and error reporting are unchanged. ## Are there any user-facing changes? Yes (test-runner UX only): * New optional timing summary output for `sqllogictests`. * New CLI flags / env vars documented in `datafusion/sqllogictest/README.md`: * `--timing-summary auto|off|top|full` / `SLT_TIMING_SUMMARY` * `--timing-top-n <N>` / `SLT_TIMING_TOP_N` * `SLT_TIMING_DEBUG_SLOW_FILES=1` (optional debug logging for slow files >30s) No public DataFusion APIs are changed. ## LLM-generated code disclosure This PR includes LLM-generated code and comments. All LLM-generated content has been manually reviewed and tested.
Apache DataFusion
DataFusion is an extensible query engine written in Rust that uses Apache Arrow as its in-memory format.
This crate provides libraries and binaries for developers building fast and feature-rich database and analytic systems, customized for particular workloads. See use cases for examples. The following related subprojects target end users:
- DataFusion Python offers a Python interface for SQL and DataFrame queries.
- DataFusion Comet is an accelerator for Apache Spark based on DataFusion.
"Out of the box," DataFusion offers SQL and DataFrame APIs, excellent performance, built-in support for CSV, Parquet, JSON, and Avro, extensive customization, and a great community.
DataFusion features a full query planner, a columnar, streaming, multi-threaded, vectorized execution engine, and partitioned data sources. You can customize DataFusion at almost all points including additional data sources, query languages, functions, custom operators and more. See the Architecture section for more details.
Here are links to important resources:
- Project Site
- Installation
- Rust Getting Started
- Rust DataFrame API
- Rust API docs
- Rust Examples
- Python DataFrame API
- Architecture
What can you do with this crate?
DataFusion is great for building projects such as domain-specific query engines, new database platforms and data pipelines, query languages and more. It lets you start quickly from a fully working engine, and then customize those features specific to your needs. See the list of known users.
Contributing to DataFusion
Please see the contributor guide and communication pages for more information.
Crate features
This crate has several features which can be specified in your Cargo.toml.
Default features:
nested_expressions: functions for working with nested types such asarray_to_stringcompression: reading files compressed withxz2,bzip2,flate2, andzstdcrypto_expressions: cryptographic functions such asmd5andsha256datetime_expressions: date and time functions such asto_timestampencoding_expressions:encodeanddecodefunctionsparquet: support for reading the Apache Parquet formatsql: support for SQL parsing and planningregex_expressions: regular expression functions, such asregexp_matchunicode_expressions: include Unicode-aware functions such ascharacter_lengthunparser: enables support to reverse LogicalPlans back into SQLrecursive_protection: uses recursive for stack overflow protection.
Optional features:
avro: support for reading the Apache Avro formatbacktrace: include backtrace information in error messagesparquet_encryption: support for using Parquet Modular Encryptionserde: enable arrow-schema'sserdefeature
DataFusion API Evolution and Deprecation Guidelines
Public methods in Apache DataFusion evolve over time: while we try to maintain a stable API, we also improve the API over time. As a result, we typically deprecate methods before removing them, according to the deprecation guidelines.
Dependencies and Cargo.lock
Following the guidance on committing Cargo.lock files, this project commits
its Cargo.lock file.
CI uses the committed Cargo.lock file, and dependencies are updated regularly
using Dependabot PRs.