It is preferable to avoid hard bindings to some exact scripting engines. If user wants to plug in Groovy we should allow it.
As for DSL I believe it is a waste of time. Few years ago it was somewhat popular idea to create DSLs for everything, but no one actually wants to learn new quirky languages, so it it never worked out. All in all the best choice is to have a good API that can be conveniently used from any scripting language + ability to plug in any scripting engine user likes. Sergi 2017-04-25 20:31 GMT+03:00 Yury Babak <y.ch...@gmail.com>: > First of all thanks for this advice. > > And DSL/Scripting update: > > Actually it's a two separate features. The first is provide scripting from > some web ui. I think we could use web-console as ui part and JSR 223 for > scripting itself, Nashorn for JS and Jython for Python. > > And the second feature - DSL. > > For those features I've created IGNITE-5065. > > Thanks, > Yury. > > > > -- > View this message in context: http://apache-ignite- > developers.2346864.n4.nabble.com/Ignite-ML-next-steps- > IGNITE-5029-tp17096p17211.html > Sent from the Apache Ignite Developers mailing list archive at Nabble.com. >
