[
https://issues.apache.org/jira/browse/HBASE-24875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-24875.
---------------------------------
Release Note:
<!-- markdown -->
The "force" flag to various unassign commands (java api, shell, etc) has been
ignored since HBase 2. As of this change the methods that take it are now
deprecated. Downstream users should stop passing/using this flag.
The Admin and AsyncAdmin Java APIs will have the deprecated version of the
unassign method with a force flag removed in HBase 4. Callers can safely
continue to use the deprecated API until then; the internal implementation just
calls the new method.
The MasterObserver coprocessor API deprecates the `preUnassign` and
`postUnassign` methods that include the force parameter and replaces them with
versions that omit this parameter. The deprecated methods will be removed from
the API in HBase 3. Until then downstream coprocessor implementations can
safely continue to *just* implement the deprecated method if they wish; the
replacement methods provide a default implementation that calls the deprecated
method with force set to `false`.
Resolution: Fixed
> Remove the force param for unassign since it dose not take effect any more
> --------------------------------------------------------------------------
>
> Key: HBASE-24875
> URL: https://issues.apache.org/jira/browse/HBASE-24875
> Project: HBase
> Issue Type: Improvement
> Components: Client
> Reporter: Zheng Wang
> Assignee: Zheng Wang
> Priority: Major
> Fix For: 3.0.0-alpha-1, 2.4.0
>
>
> Currently unassign region in fact only close it, so not need force param any
> more.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
