Github user rdblue commented on the issue:
https://github.com/apache/spark/pull/20692
> this is not urgent based on our release schedule.
Marco is contributing this right now. It is a bad idea to ask contributors
to show up in 4 months, if we don't have a better option by then. And in my
experience, it's really hard to show up right before a release and get anything
in because the focus is on the release.
> I do not like adding the types into the plans that are already very
complex.
I see this as a critical piece of information that is missing from Spark
plans. I've had to resort to a debugger several times to see what Spark thinks
types are, and I think it is worth the extra size.
I'm all for debating the value of adding these types, but we should focus
on that question. Implementations can be fixed. And when have we ever avoided a
contribution because it was too early?
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
