You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Wellington Chevreuil (Jira)" <ji...@apache.org> on 2020/05/03 13:12:00 UTC

[jira] [Commented] (HBASE-24308) Move hbase-rsgroup code into hbase-server code

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

Wellington Chevreuil commented on HBASE-24308:
----------------------------------------------

That still looks like a major change for a minor update. HBASE-22740 is marked as resolved, so how can it be blocked? Regarding HBASE-24212, can you propose a solution that doesn't involve such major change? Seems like a simple matter of handle the failing call.

> Move hbase-rsgroup code into hbase-server code
> ----------------------------------------------
>
>                 Key: HBASE-24308
>                 URL: https://issues.apache.org/jira/browse/HBASE-24308
>             Project: HBase
>          Issue Type: Bug
>          Components: rsgroup
>    Affects Versions: 2.2.3
>            Reporter: Mohammad Arshad
>            Assignee: Mohammad Arshad
>            Priority: Major
>
> Keeping rsgroup code into separate module is causing many problem. HBASE-22740 and HBASE-24212 are blocked because of this.
> In master branch hbase-rsgroup code is already moved into hbase-server. It is better to be in sync with master branch so issue fixes can be applied on branch-2 easily.
> This jira moves hbase-rsgroup code into hbase-server as it is, does not make change in protobuff etc.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)