Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/3836#issuecomment-68348124
Although this is an experimental class, and so API methods could be
removed, I think you'd still want a decent reason to remove this method at this
point, even if it's deprecated.
Here, there is no method with the same signature in the object though, so
I'm not sure what the problem is. It's common to have many methods with the
same name in a class anyway. With reflection you differentiate them by their
method signature, so this shouldn't be an obstacle. (I think the object even
appears as a separate class `DecisionTree$` in the JVM?)
Last you'd want to make a JIRA for this too in general, but first I think
the points above would need to be answered.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
