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

Xiang Li edited comment on HBASE-21478 at 11/14/18 1:47 PM:
------------------------------------------------------------

I believe HBASE-17624 makes servers ordered by hostname then port as it 
provides compareTo() in Address class, as follow. So server does not have the 
same pain as table. Please correct me if I am wrong here.
{code}
  @Override
  public int compareTo(Address that) {
    int compare = this.getHostname().compareTo(that.getHostname());
    if (compare != 0) return compare;
    return this.getPort() - that.getPort();
  }
{code}


was (Author: water):
I believe HBASE-17624 makes servers ordered by hostname then port as it 
provides compareTo() in Address class, as follow. Please correct me if I am 
wrong here.
{code}
  @Override
  public int compareTo(Address that) {
    int compare = this.getHostname().compareTo(that.getHostname());
    if (compare != 0) return compare;
    return this.getPort() - that.getPort();
  }
{code}

> Make table sorted when displaying rsgroup info in shell and master web UI
> -------------------------------------------------------------------------
>
>                 Key: HBASE-21478
>                 URL: https://issues.apache.org/jira/browse/HBASE-21478
>             Project: HBase
>          Issue Type: Improvement
>          Components: rsgroup
>            Reporter: Xiang Li
>            Assignee: Xiang Li
>            Priority: Major
>
> Regarding the output of the command of "get_rsgoup" in hbase shell, or the 
> section of "Server Group" of HMaster's web UI, the tables are not sorted, so 
> not quite easy to read, like:
> {code}
> hbase(main):003:0> get_rsgroup 'default'
> GROUP INFORMATION
> ...
> Tables:
> table3
> ns2:table22
> table1
> ns1:table11
> ...
> {code}
> They could be sorted in the order of namespace then table name:
> {code}
> table1
> table3
> ns1:table11
> ns2:table22
> {code}



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

Reply via email to