[
https://issues.apache.org/jira/browse/TAJO-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350217#comment-14350217
]
Hudson commented on TAJO-1135:
------------------------------
SUCCESS: Integrated in Tajo-master-build #599 (See
[https://builds.apache.org/job/Tajo-master-build/599/])
TAJO-1135: Implement queryable virtual table for cluster information (jihun:
rev 6e519bcf39a526b64e62d9957404bfd8a3888486)
*
tajo-catalog/tajo-catalog-server/src/main/java/org/apache/tajo/catalog/dictionary/InfoSchemaMetadataDictionary.java
*
tajo-catalog/tajo-catalog-server/src/main/java/org/apache/tajo/catalog/dictionary/ClusterTableDescriptor.java
* CHANGES
*
tajo-core/src/test/java/org/apache/tajo/master/TestNonForwardQueryResultSystemScanner.java
*
tajo-core/src/main/java/org/apache/tajo/master/exec/NonForwardQueryResultSystemScanner.java
> 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
> Affects Versions: 0.11
> Reporter: Hyunsik Choi
> Assignee: Jihun Kang
> Fix For: 0.11
>
> Attachments: TAJO-1135.patch
>
>
> 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)
