[SPARK-44071] Define UnresolvedNode trait to reduce redundancy

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.5.0
• Fix Version/s: 3.5.0
• Component/s: Spark Core
• Assignee: Ryan Johnson
• Reporter: Ryan Johnson
• Created: 15/Jun/23 18:46
• Updated: 16/Jun/23 20:30
• Resolved: 16/Jun/23 20:30

Description

Looking at unresolved.scala, spark would benefit from an UnresolvedNode trait that various UnresolvedFoo classes could inherit from:

trait UnresolvedNode extends LogicalPlan {
  override def output: Seq[Attribute] = Nil
  override lazy val resolved = false
}

Today, the code is duplicated in ~20 locations.