From c064758bd6af74f61b6a1c8ea3a096c67c2b90d1 Mon Sep 17 00:00:00 2001 From: Klaudiusz Dembler Date: Wed, 18 Nov 2026 18:18:29 +0100 Subject: [PATCH] fix(query): stop logging a missing column at ERROR The scan returns ColumnDoesNotExist, which carries the same table and column, so the caller decides whether the miss is worth a log line. A worker serving a query for a field its chunk predates answers bad_request, and the ERROR line made that client mistake read as a worker fault in the operator's log and in Sentry. Co-Authored-By: Claude Fable 5.2 --- crates/query/src/scan/parquet/file.rs | 1 - 1 file changed, 1 deletion(-) diff --git a/crates/query/src/scan/parquet/file.rs b/crates/query/src/scan/parquet/file.rs index 471c114f..1db22200 100644 --- a/crates/query/src/scan/parquet/file.rs +++ b/crates/query/src/scan/parquet/file.rs @@ -170,7 +170,6 @@ impl TableReader for ParquetFile { if default_null_columns.map_or(false, |dnc| dnc.contains(name)) { missing_null_columns.push(name); } else { - tracing::error!("column '{}' is not found in {}", name, self.table_name); anyhow::bail!(ColumnDoesNotExist::new(self.table_name.to_string(), name)); } }