Support idea with postpone! ср, 12 дек. 2018 г. в 15:26, Yuriy Babak <y.ch...@gmail.com>:
> Dmitry, > > Yes, those changes will affect users. But we could postpone this change to > the next major release(3.0) and we could implement a simple migration tool > for the ML part. > > Regards, > Yuriy > > ср, 12 дек. 2018 г. в 15:10, Dmitriy Pavlov <dpav...@apache.org>: > > > Hi Yuri, > > > > Would it affect users? > > > > Ignite-code has separation of API classes (not internal) and internal > > stuff. Internal classes may be changed from version to version, but API > > can't be renamed/moved/and so on. What about ML? > > > > Sincerely, > > Dmitriy Pavlov > > > > вт, 11 дек. 2018 г. в 16:56, Yuriy Babak <y.ch...@gmail.com>: > > > > > Igniters, > > > > > > I want to discuss package structure for ML module. Actually I don't > like > > > our current package organization. The main problem is that we have lots > > of > > > different packages under root package. > > > > > > For examples algorithm related packages on same level like some utility > > > infrastructure packages such as environment(package with some classes > > > related with training environment). > > > > > > So I created branch [1] with example of new package structure. Please > > share > > > any feedback about this package structure and about this idea itself. > > > > > > Regards, > > > Yuriy. > > > > > > [1] - > > > > > > > > > https://github.com/YuriBabak/ignite/tree/ignite-10641/modules/ml/src/main/java/org/apache/ignite/ml > > > > > >
