[
https://issues.apache.org/jira/browse/TAJO-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14364778#comment-14364778
]
Jihun Kang commented on TAJO-1331:
----------------------------------
I put my answers with number item.
1) Yes, client knows the master node but it does not know worker nodes on tajo
cluster. This api will return the details on workers which belong to tajo
cluster. This api added for compatibility on legacy client code, and could be
used for displaying resource usage on tajo cluster.
2) Session, Database, and resource management api will have a same depth on
REST api tree, but query management would be better to place under database
magement api and tree root, I think.
> 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)
