Github user jsnowacki commented on the issue:
https://github.com/apache/spark/pull/19443
The only other reason for Python I can think of, if the above are not
compelling enough, is that the issue with function not having
call-by-column-name option is that we'll get the error only at the run-time,
due to the process of how the names and types are being mapped onto JVM code.
Which is partially related to the dynamic nature of typing in Python. So while
this is spotted on compile time in Java/Scala, which may be annoying and
considered inconsistent, in Python task may fail after hours due to this issue.
Same is true for R (and SQL to some extent).
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
