[ 
https://issues.apache.org/jira/browse/IGNITE-11138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Dmitriev updated IGNITE-11138:
------------------------------------
    Description: 
Currently we have two example of using Machine Learning together with SQL 
implemented in IGNITE-11071 and IGNITE-11072 (see 
[this|https://github.com/apache/ignite/blob/66982167517e37dad5804d83c2665ac68047278c/examples/src/main/java/org/apache/ignite/examples/ml/sql/DecisionTreeClassificationTrainerSQLTableExample.java]
 and 
[this|https://github.com/apache/ignite/blob/66982167517e37dad5804d83c2665ac68047278c/examples/src/main/java/org/apache/ignite/examples/ml/sql/DecisionTreeClassificationTrainerSQLInferenceExample.java]
 example). These examples are very verbose so far and our goal is to move 
utility code into "ml" module.

The list of assumed improvements:
 * Add SQLFeatureLabelExtractor that simplifies specification of BinaryObject 
feature/label extraction approaches;
 * Simplify IgniteModel saving so that user is able so save pre-trained model 
using one function call;
 * Move SQLFunctions class that defines functions that extend SQL functionality 
into "ml" module so that user is able to use it out-of-the-box;
 * Reflect all these changes in correspondent examples.

  was:
We want to have an implementation for model predict for SQL queries.

 

Currently we have two example of using Machine Learning together with SQL 
implemented in IGNITE-11071 and IGNITE-11072 (see 
[this|https://github.com/apache/ignite/blob/66982167517e37dad5804d83c2665ac68047278c/examples/src/main/java/org/apache/ignite/examples/ml/sql/DecisionTreeClassificationTrainerSQLTableExample.java]
 and 
[this|https://github.com/apache/ignite/blob/66982167517e37dad5804d83c2665ac68047278c/examples/src/main/java/org/apache/ignite/examples/ml/sql/DecisionTreeClassificationTrainerSQLInferenceExample.java]
 example). These examples are very verbose so far and our goal is to move 
utility code into "ml" module.

The list of assumed improvements:
 * Add SQLFeatureLabelExtractor that simplifies specification of BinaryObject 
feature/label extraction approaches;
 * Simplify IgniteModel saving so that user is able so save pre-trained model 
using one function call;
 * Move SQLFunctions class that defines functions that extend SQL functionality 
into "ml" module so that user is able to use it out-of-the-box;
 * Reflect all these changes in correspondent examples.


> [ML] Predict from SQL
> ---------------------
>
>                 Key: IGNITE-11138
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11138
>             Project: Ignite
>          Issue Type: Improvement
>          Components: ml
>            Reporter: Yury Babak
>            Assignee: Anton Dmitriev
>            Priority: Major
>             Fix For: 2.8
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently we have two example of using Machine Learning together with SQL 
> implemented in IGNITE-11071 and IGNITE-11072 (see 
> [this|https://github.com/apache/ignite/blob/66982167517e37dad5804d83c2665ac68047278c/examples/src/main/java/org/apache/ignite/examples/ml/sql/DecisionTreeClassificationTrainerSQLTableExample.java]
>  and 
> [this|https://github.com/apache/ignite/blob/66982167517e37dad5804d83c2665ac68047278c/examples/src/main/java/org/apache/ignite/examples/ml/sql/DecisionTreeClassificationTrainerSQLInferenceExample.java]
>  example). These examples are very verbose so far and our goal is to move 
> utility code into "ml" module.
> The list of assumed improvements:
>  * Add SQLFeatureLabelExtractor that simplifies specification of BinaryObject 
> feature/label extraction approaches;
>  * Simplify IgniteModel saving so that user is able so save pre-trained model 
> using one function call;
>  * Move SQLFunctions class that defines functions that extend SQL 
> functionality into "ml" module so that user is able to use it out-of-the-box;
>  * Reflect all these changes in correspondent examples.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to