Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/20618
Maybe I am too much caring about this and It guess it wouldn't be a big
change; however, I was thinking there might be subtle nits, like, referring
`java.lang.Math*` in Python side and R side which is not preferred up to my
knowledge.
Just wanted to avoid another iteration for finding a better description for
both Python and R again here. (Just noticed it's his very first contribution to
Spark too.).
Seems fine for SQL / Scala / Java as they already use a fully qualified
class name, for example, in case of SQL:
```sql
spark-sql> DESCRIBE FUNCTION EXTENDED cos;
...
Function: cos
Class: org.apache.spark.sql.catalyst.expressions.Cos
...
```
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
