[
https://issues.apache.org/jira/browse/HBASE-23647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17080967#comment-17080967
]
Bharath Vissapragada commented on HBASE-23647:
----------------------------------------------
bq. So both this one and HBASE-24156 retain fixVersion 2.3.0.
Well, the problem is that whoever comes across this jira and sees the fix
version has 2.3.0 thinks that the feature is enabled by default in 2.3.0 (given
the title of this jira). Thats the reason I removed from here and added in
HBASE-24156.
bq. Can we make sure the set of release notes and jira subjects make clear that
this registry is not the defualts implementation on 2.3? That's my only concern.
This is a better idea. I'll can change the jira subject and add release notes
unless there are any objections.
> Make MasterRegistry the default registry impl
> ---------------------------------------------
>
> Key: HBASE-23647
> URL: https://issues.apache.org/jira/browse/HBASE-23647
> Project: HBase
> Issue Type: Sub-task
> Components: Client
> Affects Versions: 3.0.0
> Reporter: Bharath Vissapragada
> Assignee: Bharath Vissapragada
> Priority: Major
> Fix For: 3.0.0, HBASE-18095
>
>
> Now that we are close to getting the registry implementation patch in, the
> idea here is to make it the default implementation in 3.0.0 and this means
> - No known bugs with the implementation
> - No known performance issues
> - Entire nightly test suite is green (and without flakes).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
