The active config object within the current scope. See SQLConf.get for more information.

Deduplicates missing expressions by ExprId.

Insert the missing expressions in the output list of the operator. Recursively call expandOperatorsOutputList to expand the output lists of Projects and Aggregates below the current one. In order to stay compatible with fixed-point, missing expressions are inserted after the original output list, but before any qualified access only columns that have been added as part of resolution from hidden output.

Only AttributeReferences are propagated recursively in expandOperatorsOutputList. Aliases are meant to be inserted in the topmost operator. For example, SortResolver may push down aliased aggregate and grouping expression trees to the immediate Aggregate below, but it does not make sense to push them down further:

-- The MAX(v2.col1) aggregate has to be pushed down to [[Aggregate]], but not to [[Project]]
-- below it.
SELECT COUNT(col1) FROM v1 NATURAL JOIN v2 GROUP BY col1 ORDER BY MAX(v2.col1);

->

Project [count(col1)#23L]
+- Sort [max(col1)#25 ASC NULLS FIRST], true
  +- Aggregate [col1#21], [count(col1#21) AS count(col1)#23L, max(col1#20) AS max(col1)#25]
    +- Project [col1#21, col1#20]
      ...

Resolve Filter by resolving its child and its condition. If an attribute that is used in the condition is not present in child's output, we need to try and find the attribute in hidden output. If found, update child's output and place a Project node on top of original Filter with the original output of a Filter's child.

See ResolvesNameByHiddenOutput doc for more context.

If missingExpressions is not empty, output of an operator has been changed by insertMissingExpressions. Therefore, we need to restore the original output, by placing a Project on top of an original node, with original's node output. Additionally, we append all qualified access only columns from hidden output that were inserted as missing attributes, because they may be needed in upper operators (if not, they will be pruned away in PruneMetadataColumns). Other hidden attributes are thrown away, because we cannot reference them from the new Project (they are not outputted from below).

If SQLConf.SINGLE_PASS_RESOLVER_PREVENT_USING_ALIASES_FROM_NON_DIRECT_CHILDREN is set to true, we need to overwrite the current scope and clear aggregateListAliases and baseAggregate. This is needed in order to prevent later replacement of Sort/Having expressions using semantically equal aliased expressions from non-direct children. For example, in the following query:

SELECT col1 AS a FROM VALUES(1,2) GROUP BY col1, col2 HAVING col2 > 1 ORDER BY col1;

With flag set to false, analyzed plan will be:

Sort [a#3 ASC NULLS FIRST], true +- Project [a#3] +- Filter (col2#2 > 1) +- Aggregate [col1#1, col2#2], [col1#1 AS a#3, col2#2, col1#1] +- LocalRelation [col1#1, col2#2]

Instead of using missing attribute col1#1 we can use its alias a#3 in the Sort and avoid adding an extra projection. This is because all of Sort, Project, Filter and Aggregate belong to the same NameScope since Project was artificially inserted.

However, fixed-point can't handle this case properly and produces the following plan:

Project [a#3] +- Sort [col1#1 ASC NULLS FIRST], true +- Project [a#3, col1#1] +- Filter (col2#2 > 1) +- Aggregate [col1#1, col2#2], [col1#1 AS a#3, col2#2, col1#1] +- LocalRelation [col1#1, col2#2]

Therefore, we need to match this behavior of fixed-point in single-pass in order to avoid logical plan mismatches.

Method used to validate Filter operator. Throws in the following cases:

• If condition is invalid (based on UnsupportedExpressionInOperatorValidation.isExpressionInUnsupportedOperator check)
• If the data type of the condition is not boolean.

Sets all SQL configurations specified in pairs, calls f, and then restores all SQL configurations.