I don't think you can move or alter the class APis. There also isn't much value in copying the code. Maybe there are opportunities for moving some internal code. But in general I think all this has to wait.
On Thu, Feb 15, 2018, 5:17 AM Yacine Mazari <y.maz...@gmail.com> wrote: > Hi, > > I see that many classes under "org.apache.spark.ml" are still referring to > the "org.apache.spark.mllib" implementation. > > While there still is time until the deprecation deadline by version 3.0, > having these dependencies makes it impossible or difficult to make > improvements to these classes. > > I see that IDF and HashingTF are being migrated in SPARK-22531 and > SPARK-21748. > > 1) Should I go ahead and start with one of the following: BisectingKMeans, > KMeans, LDA, PCA, Word2Vec, > FPGrowth? I don't see any ongoing work with them. > > 2) I suggest creating an umbrella ticket to track this migration. (I > haven't > seen any) > > What do you think? > > Best Regards, > Yacine. > > > > -- > Sent from: http://apache-spark-developers-list.1001551.n3.nabble.com/ > > --------------------------------------------------------------------- > To unsubscribe e-mail: dev-unsubscr...@spark.apache.org > >
