Github user gatorsmile commented on the issue:

    https://github.com/apache/spark/pull/18576
  
    Changing the usage/semantics of `output` is risky. It could easily break 
the existing codes without notice, especially when you do not completely remove 
`output` from `QueryPlan`. 
    
    Adding nullability as a separate trait that crosses `LogicalPlan` and 
`SparkPlan` looks less intrusive. 


---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to