hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Reid Chan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-18621) Refactor ClusterOptions before applying to code base
Date Wed, 13 Sep 2017 03:35:01 GMT

     [ https://issues.apache.org/jira/browse/HBASE-18621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Reid Chan updated HBASE-18621:
    Release Note: 
Provide a new way to get desired ClusterStatus with a set of ClusterStatus.Option, such that
the response back to client can be limited.
Note that, the constructor way to new a ClusterStatus will be no longer support after 2.0.0,
 and use ClusterStatus.Builder instead.

> 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
>             Fix For: 2.0.0-beta-1
>         Attachments: HBASE-18621.master.001.patch, HBASE-18621.master.002.patch, HBASE-18621.master.003.patch,
HBASE-18621.master.004.patch, HBASE-18621.master.005.patch, HBASE-18621.master.006.patch,
HBASE-18621.master.007.patch, HBASE-18621.master.008.patch, HBASE-18621.master.009.patch,
HBASE-18621.master.010.patch, HBASE-18621.master.011.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

View raw message