You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lens.apache.org by "Jaideep Dhok (JIRA)" <ji...@apache.org> on 2015/07/01 20:21:04 UTC
[jira] [Comment Edited] (LENS-581) Revisit Lens ML API
[ https://issues.apache.org/jira/browse/LENS-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14610768#comment-14610768 ]
Jaideep Dhok edited comment on LENS-581 at 7/1/15 6:20 PM:
-----------------------------------------------------------
+1 for using lightweight db library instead of JPA which is overkill for this. Using JDBC directly is very painful. There is also Spring's jdbcTemplate, although downside is we have to add a big Spring dependency.
[~sharadag] We are already using Apache dbutils in lens server module. Would that be sufficient? Otherwise we have two different libraries for the same purpose in different modules.
was (Author: jaideepdhok):
+1 for using lightweight db layer instead of JPA which is overkill for this.
[~sharadag] We are already using Apache dbutils in lens server module. Would that be sufficient? Otherwise we have two different libraries for the same purpose in different modules.
> 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
> Assignee: vikas singh
> Labels: patch
>
> - 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)