hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Drob (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18621) Refactor ClusterOptions before applying to code base
Date Tue, 22 Aug 2017 15:00:01 GMT

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

Mike Drob commented on HBASE-18621:
-----------------------------------

Sure...

{code}
enum Status {
  // this doesn't change from your patch
}

ClusterStatus getClusterStatus(EnumSet<Status> statuses) {
  ...
}
{code}

Than a client that wants to get all the metrics would do {{getClusterStatus(EnumSet.allOf(Status.class))}}
and if you want one particular metric it would be {{EnumSet.of(Status.MASTER)}}


> Refactor ClusterOptions before applying to code base
> ----------------------------------------------------
>
>                 Key: HBASE-18621
>                 URL: https://issues.apache.org/jira/browse/HBASE-18621
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Reid Chan
>            Assignee: Reid Chan
>         Attachments: HBASE-18621.master.001.patch, HBASE-18621.master.002.patch, HBASE-18621.master.003.patch
>
>
> So far, ClusterStatus.Options is not so clean that can be applied to code base.
> Refactoring it before next move.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message