You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Billy(Yiming) Liu (JIRA)" <ji...@apache.org> on 2016/10/10 14:58:21 UTC
[jira] [Closed] (KYLIN-2039) Refactor REST Request/Response Object
into standalone library
[ https://issues.apache.org/jira/browse/KYLIN-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Billy(Yiming) Liu closed KYLIN-2039.
------------------------------------
Resolution: Won't Fix
REST API could not guarantee the response body has the format backward compatible. So just leave the interface contract as simple as possible, to string only, not POJO objects.
> Refactor REST Request/Response Object into standalone library
> -------------------------------------------------------------
>
> Key: KYLIN-2039
> URL: https://issues.apache.org/jira/browse/KYLIN-2039
> Project: Kylin
> Issue Type: Improvement
> Components: REST Service
> Reporter: Billy(Yiming) Liu
> Assignee: Zhong,Jason
> Priority: Minor
>
> Currently, the Request/Response objects locate at server-base project under org/apache/kylin/rest/request[response,model]. They are POJOs which are used to communicate between any REST client and Kylin Server. If someone wants to integrate Kylin by REST API, he has to import kylin-server library. The kylin-server is the project to host the Query/Job web server. This is library will introduce almost all kylin backend libraries indirectly(by pom dependency). But those are not the required components in client side. So I will suggest refactoring some REST code into standalone lightweight library, and make the client-server communication much easier.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)