[
https://issues.apache.org/jira/browse/TAJO-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14317358#comment-14317358
]
Jakob Homan commented on TAJO-1331:
-----------------------------------
It's not a blocker, but it would be nice if the REST spec were codified in some
way that made it easier to verify correctness and generate clients. Both
[swagger|http://swagger.io/] and [RAML|http://raml.org/] provide useful ways of
expressing the REST spec. This could certainly be done after the initial work
was completed.
> Add REST Client API
> -------------------
>
> Key: TAJO-1331
> URL: https://issues.apache.org/jira/browse/TAJO-1331
> Project: Tajo
> Issue Type: New Feature
> Components: client
> Reporter: Hyunsik Choi
> Assignee: Jihun Kang
> Attachments: TajoClientRestAPIDesign_draft.pdf
>
>
> Currently, there is only protobuf-based TCP protocol for client. It works
> well.
> However, even though protobuf itself is very portable, our protobuf-based
> client protocol is is not portable. This is because protocol buffer does not
> provide RPC implementation and it just provides RPC stub and marshalling
> method.
> The main objective of this issue is to implement RESTful API for client. This
> technique is very widely used in many applications. REST does not require any
> heavy dependency. It is expected that many third-party client API can be
> easily implemented with REST client API.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
