-
Notifications
You must be signed in to change notification settings - Fork 28.5k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[SPARK-26459][SQL] replace UpdateNullabilityInAttributeReferences wit…
…h FixNullability ## What changes were proposed in this pull request? This is a followup of #18576 The newly added rule `UpdateNullabilityInAttributeReferences` does the same thing the `FixNullability` does, we only need to keep one of them. This PR removes `UpdateNullabilityInAttributeReferences`, and use `FixNullability` to replace it. Also rename it to `UpdateAttributeNullability` ## How was this patch tested? existing tests Closes #23390 from cloud-fan/nullable. Authored-by: Wenchen Fan <[email protected]> Signed-off-by: Takeshi Yamamuro <[email protected]>
- Loading branch information
Showing
4 changed files
with
65 additions
and
57 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
57 changes: 57 additions & 0 deletions
57
...st/src/main/scala/org/apache/spark/sql/catalyst/analysis/UpdateAttributeNullability.scala
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,57 @@ | ||
/* | ||
* 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. | ||
*/ | ||
|
||
package org.apache.spark.sql.catalyst.analysis | ||
|
||
import org.apache.spark.sql.catalyst.expressions.Attribute | ||
import org.apache.spark.sql.catalyst.plans.logical.{LeafNode, LogicalPlan} | ||
import org.apache.spark.sql.catalyst.rules.Rule | ||
|
||
/** | ||
* Updates nullability of Attributes in a resolved LogicalPlan by using the nullability of | ||
* corresponding Attributes of its children output Attributes. This step is needed because | ||
* users can use a resolved AttributeReference in the Dataset API and outer joins | ||
* can change the nullability of an AttribtueReference. Without this rule, a nullable column's | ||
* nullable field can be actually set as non-nullable, which cause illegal optimization | ||
* (e.g., NULL propagation) and wrong answers. | ||
* See SPARK-13484 and SPARK-13801 for the concrete queries of this case. | ||
* | ||
* This rule should be executed again at the end of optimization phase, as optimizer may change | ||
* some expressions and their nullabilities as well. See SPARK-21351 for more details. | ||
*/ | ||
object UpdateAttributeNullability extends Rule[LogicalPlan] { | ||
|
||
def apply(plan: LogicalPlan): LogicalPlan = plan resolveOperatorsUp { | ||
// Skip unresolved nodes. | ||
case p if !p.resolved => p | ||
// Skip leaf node, as it has no child and no need to update nullability. | ||
case p: LeafNode => p | ||
case p: LogicalPlan => | ||
val nullabilities = p.children.flatMap(c => c.output).groupBy(_.exprId).map { | ||
// If there are multiple Attributes having the same ExprId, we need to resolve | ||
// the conflict of nullable field. We do not really expect this to happen. | ||
case (exprId, attributes) => exprId -> attributes.exists(_.nullable) | ||
} | ||
// For an Attribute used by the current LogicalPlan, if it is from its children, | ||
// we fix the nullable field by using the nullability setting of the corresponding | ||
// output Attribute from the children. | ||
p.transformExpressions { | ||
case attr: Attribute if nullabilities.contains(attr.exprId) => | ||
attr.withNullability(nullabilities(attr.exprId)) | ||
} | ||
} | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters