Github user MLnick commented on the issue:

    https://github.com/apache/spark/pull/15831
  
    I'm also generally supportive of (1) - porting the code to `ml` and having 
the `mllib` code wrap the `ml` version - this is the approach for other models 
that have been done. Of course only once *all* `mllib` code has been ported 
over fully can we ultimately deprecate `mllib`.
    
    I guess we can start doing this for some transformers like these - but 
ideally we should focus on porting stuff that's still missing in `ml` first. 
    
    I'd prefer that we create a top-level JIRA to track all the components that 
need to be done, and link everything appropriately. We also need to decide on 
priority - we may realistically be working on it over a 1-1.5 year time frame.


---
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

Reply via email to