[
https://issues.apache.org/jira/browse/TAJO-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14364677#comment-14364677
]
Seungun Choe commented on TAJO-1331:
------------------------------------
The API design looks good for us.
But, I have two question.
1) Why Resource Management makes for client?
I think it not necessary.
Client knows just tajo-master. Isn't it?
2) Please show me about REST resource tree architecture. (Are Session, QueryID,
DB Management and Resource Management's tree depth same?)
> 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,
> TajoClientRestAPIDesign_v0.1.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 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)
