Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/20692
My 2 cents: a data source may have a lot of columns, and a column may be a
complex struct type. So embedding the type in the plan may make the plan
unreadable.
If I'm debugging and see a complex plan with attribute types inside the
plan, it will be really hard to extract the information I want from the plan,
as the plan node may across many lines and hard to read.
Since attributes are unique across the query plan, I think put a list of
"attribute -> type" before or after the explain result is acceptable.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
