[
https://issues.apache.org/jira/browse/TAJO-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14296592#comment-14296592
]
ASF GitHub Bot commented on TAJO-1135:
--------------------------------------
GitHub user ykrips opened a pull request:
https://github.com/apache/tajo/pull/366
TAJO-1135: Implement queryable virtual table for cluster information
This virtual table will be shown like following.
```
information_schema> select * from workers;
host, port, type, status, total_cpu, used_mem, total_mem, free_heap,
max_heap, used_diskslots, total_diskslots, running_tasks, heartbeat
-------------------------------
hostnameA, 28093, QueryMaster, RUNNING, , , , 130004408, 932118528,
, , 0, 2015-01-29 17:09:18.859999
hostnameA, 28091, Worker, RUNNING, 1, 0, 1024, 130004408,
932118528, 0.0, 1.0, 0, 2015-01-29 17:09:18.859999
(2 rows, 0.025 sec, 0 B selected)
```
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ykrips/tajo TAJO-1135
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/366.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #366
----
commit 0217440de6bfeac45a175663dec23bd732b22904
Author: Jihun Kang <[email protected]>
Date: 2015-01-29T08:16:18Z
TAJO-1135: Implement queryable virtual table for cluster information
----
> 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)
