[ 
https://issues.apache.org/jira/browse/HBASE-13718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14552773#comment-14552773
 ] 

Hadoop QA commented on HBASE-13718:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12734170/D38649.diff.txt
  against master branch at commit 88f19ab6979c7012c3dd22b2f45db9f746c7736d.
  ATTACHMENT ID: 12734170

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+0 tests included{color}.  The patch appears to be a 
documentation, build,
                        or dev-support patch that doesn't require tests.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/14117//console

This message is automatically generated.

> Add a pretty printed table description to the table detail page of HBase's 
> master
> ---------------------------------------------------------------------------------
>
>                 Key: HBASE-13718
>                 URL: https://issues.apache.org/jira/browse/HBASE-13718
>             Project: HBase
>          Issue Type: Improvement
>          Components: hbase
>    Affects Versions: 2.0.0
>            Reporter: Joao Girao
>            Assignee: Joao Girao
>            Priority: Minor
>             Fix For: 2.0.0, 1.2.0
>
>         Attachments: D38649.diff.txt
>
>
> HBase's master has an info server that's useful for debugging and getting a 
> general overview of what's in the cluster. It has a page dedicated to 
> describing a cluster. You can reach it by going to something like: 
> http://localhost:54677/table.jsp?name=cluster_test
> That page currently doesn't have anything about the current table schema. It 
> would be nice to have a table that lists the different column families and 
> how they are set up.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to