Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/14539
@eyalfa I am a bit hesitant to add yet another almost pointless
`LogicalPlan` node to Catalyst, and certainly not one that is functionally
exactly the same as a `Union`. This would require us to add another rule to the
analyzer/optimizer and we would have to add a separate case to type coercion.
I do think your point has merit and that errors should be as concise as
possible, but I would (if we were to change this) rather add some sort of an
alias which encodes this information or just add a flag to Union.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
