From 28981a87e55bf27b983b7fe1aaffc3fecadad759 Mon Sep 17 00:00:00 2001 From: Heran Lin Date: Tue, 3 Mar 2026 14:49:01 +0800 Subject: [PATCH] fix: make the `sql` feature truly optional (#20625) ## Which issue does this PR close? N/A ## Rationale for this change When enabling the `recursive_protection` feature for the `datafusion` crate, the `sql` feature is enabled. This is undesirable if the downstream project would like the `sql` feature to be off. ## What changes are included in this PR? Use the `?` syntax for features of dependencies for `recursive_protection`. This was already correctly done for other features such as `unicode_expressions`. ## Are these changes tested? N/A ## Are there any user-facing changes? This makes dependency management better for downstream projects and is not a breaking change. --- datafusion/core/Cargo.toml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/datafusion/core/Cargo.toml b/datafusion/core/Cargo.toml index 3d0a76a182697..8965948a0f4e2 100644 --- a/datafusion/core/Cargo.toml +++ b/datafusion/core/Cargo.toml @@ -88,8 +88,8 @@ recursive_protection = [ "datafusion-optimizer/recursive_protection", "datafusion-physical-optimizer/recursive_protection", "datafusion-physical-expr/recursive_protection", - "datafusion-sql/recursive_protection", - "sqlparser/recursive-protection", + "datafusion-sql?/recursive_protection", + "sqlparser?/recursive-protection", ] serde = [ "dep:serde",