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

Hudson commented on HBASE-16848:
--------------------------------

Results for branch branch-2.0
        [build #80 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/80/]: 
(x) *{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/80//General_Nightly_Build_Report/]




(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/80//JDK8_Nightly_Build_Report_(Hadoop2)/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/80//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


> Usage for show_peer_tableCFs command doesn't include peer
> ---------------------------------------------------------
>
>                 Key: HBASE-16848
>                 URL: https://issues.apache.org/jira/browse/HBASE-16848
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Ted Yu
>            Assignee: Peter Somogyi
>            Priority: Minor
>              Labels: documentation, replication, shell
>             Fix For: 3.0.0, 2.1.0, 1.5.0, 1.2.7, 1.4.3, 2.0.0
>
>         Attachments: HBASE-16848.master.001.patch, 
> HBASE-16848.master.001.patch
>
>
> {code}
> hbase(main):003:0> show_peer_tableCFs
> ERROR: wrong number of arguments (0 for 1)
> Here is some help for this command:
>   Show replicable table-cf config for the specified peer.
>     hbase> show_peer_tableCFs
> {code}
> The sample usage should include peer id.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to