Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/17807
right, there's a bunch of *Col in ml. I think people would associate `col`
to a reference to a/another column in the dataframe
I do see your point about `is_grouping`, and also that `grouping_id` is not
a substitute. It is unfortunate R's `grouping` is conflicting with this. I'm
not sure if I have a good name suggestion. We in occasion have workaround issue
like this - since this is S3 method we could add a generic etc to route the
call to get it to be compatible. do think in this case it is worthwhile to do
though?
---
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
