Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/20692
Normally, in our Spark community, if the contributor is not available when
we decide to merge, the others (including the committers) will take it over and
give the credit back the contributor.
If this is critical in your usage scenario before our Spark 2.4 is out, I
think you can add the patch to your fork.
We should output the data types, but not embed them in the plans. However,
I do not know which is the best solution and that is why I am asking @mgaido91
to do more investigation.
http://db2commerce.com/2013/06/11/explain-part-2-command-line-explain-plans-using-db2exfmt/
is just an example.
Hopefully, you can be also involved in the design discussion of our new
formatted output of EXPLAIN.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
