[jira] [Comment Edited] (LENS-581) Revisit Lens ML API

["Himanshu Gahlaut (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LENS-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14591344#comment-14591344 ] 

Himanshu Gahlaut edited comment on LENS-581 at 6/18/15 6:39 AM:
----------------------------------------------------------------

Is Java Persistence APIs 2.0 under consideration ? They neatly abstract out connection management and SQL for CRUD operations.  Code becomes a lot more easier to understand and maintain. Also underlying DB can be switched when required without changing code. E.g.: If em is an entity manager instance, then instead of writing an INSERT query,  calling em.persist(entity) will store the record (entity) in underlying DB. 


was (Author: himanshu.gahlaut):
Is Java Persistence APIs 2.0 under consideration ? They neatly abstract out connection management and SQL for CRUD operations.  Code becomes a lot more easier to understand and maintain. Also underlying DB can be switched when required without changing code. E.g.: If em is an entity manager instance, then instead of writing an INSERT query,  calling em.persist(entity) with store the record (entity) in underlying DB. 

> Revisit Lens ML API
> -------------------
>
>                 Key: LENS-581
>                 URL: https://issues.apache.org/jira/browse/LENS-581
>             Project: Apache Lens
>          Issue Type: Improvement
>          Components: ml
>            Reporter: Sharad Agarwal
>
> - Currently all API assume synchronous behaviour. Give ability to return handle and status object
> - Improve Algorithm and Training APIs : some of the server side and client side classes are not very clear



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)