[
https://issues.apache.org/jira/browse/TAJO-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350036#comment-14350036
]
Tajo QA commented on TAJO-1135:
-------------------------------
{color:red}*-1 overall.*{color} Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12702988/TAJO-1135.patch
against master revision release-0.9.0-rc0-185-g1617fa9.
{color:green}+1 @author.{color} The patch does not contain any @author
tags.
{color:green}+1 tests included.{color} The patch appears to include 1 new
or modified test files.
{color:green}+1 javac.{color} The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc.{color} The applied patch does not increase the
total number of javadoc warnings.
{color:green}+1 checkstyle.{color} The patch generated 0 code style errors.
{color:red}-1 findbugs.{color} The patch appears to cause Findbugs
(version 2.0.3) to fail.
{color:green}+1 release audit.{color} The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests.{color} The patch passed unit tests in
tajo-catalog/tajo-catalog-server tajo-core.
Test results:
https://builds.apache.org/job/PreCommit-TAJO-Build/600//testReport/
Findbugs results:
https://builds.apache.org/job/PreCommit-TAJO-Build/600//findbugsResult
Console output: https://builds.apache.org/job/PreCommit-TAJO-Build/600//console
This message is automatically generated.
> 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)
