Ignite ML, DSL/Scripting (IGNITE-5065)

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Ignite ML, DSL/Scripting (IGNITE-5065)

Yuriy Babak
Hi all!

Currently I'm working on adding scripting support for Ignite ML(IGNITE-5065). The basic idea is to provide possibility to create and run some scripts with ML algorithms over Ignite cluster using Ignite ML API and JS/Python as script language.

I’ve exchanged several thoughts with Alexey K., Ignite web console maintainer and according to him it's okey to add this feature to web-console module.

In this case we should add dependency to Ignite ML which require Java8.

On the other hand we could create new UI module for this purpose but it will require additional time for development separate ml web console.

If anyone know addition pros/cons for both ways - please advise.

Thanks,
Yury Babak.
Reply | Threaded
Open this post in threaded view
|

Re: Ignite ML, DSL/Scripting (IGNITE-5065)

Sergi
I'm a bit out of the loop with ML and Web console, but Java scripting
engines as in JSR-233 are supported in Java 7. You can use JSR-233 API in
Web Console, implementation will be in IgniteML module, which requires Java
8 anyways. This way they will be decoupled.

Does this work for you?

Sergi

2017-04-25 21:12 GMT+03:00 Yury Babak <[hidden email]>:

> Hi all!
>
> Currently I'm working on adding scripting support for Ignite
> ML(IGNITE-5065). The basic idea is to provide possibility to create and run
> some scripts with ML algorithms over Ignite cluster using Ignite ML API and
> JS/Python as script language.
>
> I’ve exchanged several thoughts with Alexey K., Ignite web console
> maintainer and according to him it's okey to add this feature to
> web-console
> module.
>
> In this case we should add dependency to Ignite ML which require Java8.
>
> On the other hand we could create new UI module for this purpose but it
> will
> require additional time for development separate ml web console.
>
> If anyone know addition pros/cons for both ways - please advise.
>
> Thanks,
> Yury Babak.
>
>
>
> --
> View this message in context: http://apache-ignite-
> developers.2346864.n4.nabble.com/Ignite-ML-DSL-Scripting-
> IGNITE-5065-tp17216.html
> Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
>
Reply | Threaded
Open this post in threaded view
|

Re: Ignite ML, DSL/Scripting (IGNITE-5065)

dmagda
Folks,

Isn’t it to early to dig into DSL implementation? I would take this path only after Ignite supports basic algorithms used for ML and predictive analysis so that people can use it somehow. Then depending on a feedback we might need to start on this task.


Denis

> On Apr 25, 2017, at 12:38 PM, Sergi Vladykin <[hidden email]> wrote:
>
> I'm a bit out of the loop with ML and Web console, but Java scripting
> engines as in JSR-233 are supported in Java 7. You can use JSR-233 API in
> Web Console, implementation will be in IgniteML module, which requires Java
> 8 anyways. This way they will be decoupled.
>
> Does this work for you?
>
> Sergi
>
> 2017-04-25 21:12 GMT+03:00 Yury Babak <[hidden email]>:
>
>> Hi all!
>>
>> Currently I'm working on adding scripting support for Ignite
>> ML(IGNITE-5065). The basic idea is to provide possibility to create and run
>> some scripts with ML algorithms over Ignite cluster using Ignite ML API and
>> JS/Python as script language.
>>
>> I’ve exchanged several thoughts with Alexey K., Ignite web console
>> maintainer and according to him it's okey to add this feature to
>> web-console
>> module.
>>
>> In this case we should add dependency to Ignite ML which require Java8.
>>
>> On the other hand we could create new UI module for this purpose but it
>> will
>> require additional time for development separate ml web console.
>>
>> If anyone know addition pros/cons for both ways - please advise.
>>
>> Thanks,
>> Yury Babak.
>>
>>
>>
>> --
>> View this message in context: http://apache-ignite-
>> developers.2346864.n4.nabble.com/Ignite-ML-DSL-Scripting-
>> IGNITE-5065-tp17216.html
>> Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
>>