Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/13403#issuecomment-222614982
Thank you for review again @rxin.
Actually, I fully understand and expect your decision.
The reason why I making this issue is I think we need explicit discussions
and the conclusion for this issue.
I worried that Spark shows this inconsistency forever implicitly. As we
know, if we do not this in Spark 2.0, this will happen on Spark 3.0 or maybe
never because of the same reason.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
