Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18737
Yea. The test failure above itself is legitimate but while manually running
and debugging few more tests with some more fixes, it printed:
```
Failed
-------------------------------------------------------------------------
1. Error: spark.glm and predict (@test_basic.R#56)
-----------------------------
org.apache.spark.sql.AnalysisException: Cannot resolve column name
"Sepal.Length" among (Sepal.Length, Sepal.Width, Petal.Length, Petal.Width,
Species, stridx_72b2d3986ee9, onehot_9b2382c39190);
at
org.apache.spark.sql.Dataset$$anonfun$resolve$1.apply(Dataset.scala:218)
at
org.apache.spark.sql.Dataset$$anonfun$resolve$1.apply(Dataset.scala:218)
```
The cause looks trying to resolve the dot as a nested column access in some
places (like `Dataset.col`) and looks not in others.
Yea.... will maybe start a thread on a mailing list after investigating
more later.
---
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
