[
https://issues.apache.org/jira/browse/TAJO-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257843#comment-14257843
]
Hyunsik Choi commented on TAJO-1228:
------------------------------------
I'll change QueryInProgress and QueryInfo as follows:
* Add TableDesc to TajoHeartBeat message.
* buildTajoHeartBeat sets TableDesc of result set TajoHeartBeat if a query is
succeeded
* If the query is one of terminal state and heartbeat message includes
TableDesc, QueryInProgress::heartbeat sets the result to QueryInfo.
Also, I'll change QueryClientImpl to get a running query status and a query
result from TajoMaster.
> TajoClient should communicate with only TajoMaster without TajoWorker
> ---------------------------------------------------------------------
>
> Key: TAJO-1228
> URL: https://issues.apache.org/jira/browse/TAJO-1228
> Project: Tajo
> Issue Type: Bug
> Components: client
> Reporter: Hyunsik Choi
> Assignee: Hyunsik Choi
> Fix For: 0.10
>
>
> Currently, TajoClient connects with TajoMaster as well as TajoWorker. A query
> submission is passed from TajoClient to TajoMaster, and than TajoMaster
> forwards the query to one query master running on a TajoWorker. After than, a
> client monitors the query progress through the query master.
> In other words, TajoClient contacts both TajoMaster and TajoWorker. It has
> three disadvantages:
> * a network firewall should allow connections to TajoWorker nodes.
> * all components should have complex states and communication logic one
> another.
> * TAJO-1160 is trying to remove hadoop dependency from TajoClient. In
> TAJO-1160, TajoClient will use only some server which forwards query results
> to itself instead of reading directly HDFS. TajoMaster would be the best
> component to forward the query results because TajoClient always connects
> with TajoMaster. So, if TajoClient communicates with only TajoMaster, all
> client logic and protocol would be simple.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
