[
https://issues.apache.org/jira/browse/TAJO-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14309028#comment-14309028
]
ASF GitHub Bot commented on TAJO-1135:
--------------------------------------
Github user jihoonson commented on the pull request:
https://github.com/apache/tajo/pull/366#issuecomment-73225187
Hi @ykrips, thanks for your work.
In overall, the patch looks good to me.
Only one thing I want to suggest is the table name.
Since the newly added table contains the information of query masters as
well as workers, I think that ```cluster``` is the more proper name than
```workers```.
What do you think about it?
> Implement queryable virtual table for cluster information
> ---------------------------------------------------------
>
> Key: TAJO-1135
> URL: https://issues.apache.org/jira/browse/TAJO-1135
> Project: Tajo
> Issue Type: New Feature
> Components: tajo master
> Reporter: Hyunsik Choi
> Assignee: Jihun Kang
>
> Currently, Tajo does not provide queryable cluster information. We just can
> display cluster nodes through 'bin/tajo cluster' inline command.
> I propose that TajoMaster should maintain a queryable virtual table where
> each row represents each cluster node and columns should contain hostname,
> resource, last ping, and so on. The virtual table should be processed by API
> and SQL.
> Users can discovery cluster information in ad-hoc manner. Also, internal Tajo
> system can make good use of the virtual table for scheduling resources or
> displaying cluster information in WEB UI. I also expect that this feature
> also simplify the many parts related to cluster information.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)