1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
// Licensed to the Apache Software Foundation (ASF) under one
// or more contributor license agreements. See the NOTICE file
// distributed with this work for additional information
// regarding copyright ownership. The ASF licenses this file
// to you under the Apache License, Version 2.0 (the
// "License"); you may not use this file except in compliance
// with the License. You may obtain a copy of the License at
//
// http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing,
// software distributed under the License is distributed on an
// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
// KIND, either express or implied. See the License for the
// specific language governing permissions and limitations
// under the License.
//! Analyzer rules layered on top of DataFusion's defaults.
use Result;
use ConfigOptions;
use LogicalPlan;
use AnalyzerRule;
/// Resolve [`LambdaVariable`] references into bound lambda parameters.
///
/// DataFusion's SQL planner resolves lambda variables inline as it plans a
/// higher-order function call, so SQL-built plans never carry unresolved
/// variables. Plans assembled programmatically through the Python expression
/// builder (e.g. `array_transform(col("xs"), lambda_(["v"], lambda_var("v")))`)
/// do carry them, and nothing in the default analyzer resolves them. This rule
/// runs [`LogicalPlan::resolve_lambda_variables`] so both construction paths
/// reach the optimizer with bound lambdas.
///
/// [`LambdaVariable`]: datafusion::logical_expr::expr::LambdaVariable