[
https://issues.apache.org/jira/browse/HBASE-13537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14516451#comment-14516451
]
Anoop Sam John commented on HBASE-13537:
----------------------------------------
Is this binary compatibility break ok (with out deprecation in a previous major
version)? cc [~busbey]
When we have to change the return type of a method and deprecate the old one,
we have to add the new method (obviously the name will have to be different)
and deprecate old one.
In effect when we change the return type from void to Future<T>, it is like we
remove a method and add a new method. At least for the run time.
> Change the admin interface for async operations to return Future.
> -----------------------------------------------------------------
>
> Key: HBASE-13537
> URL: https://issues.apache.org/jira/browse/HBASE-13537
> Project: HBase
> Issue Type: Sub-task
> Components: proc-v2
> Affects Versions: 2.0.0
> Reporter: Srikanth Srungarapu
> Assignee: Srikanth Srungarapu
> Fix For: 2.0.0
>
> Attachments: HBASE-13537.patch, HBASE-13537.patch, HBASE-13537.patch,
> HBASE-13537_v2.patch
>
>
> At the moment, the async operations are returning void. This task aims to
> change the return type to Future and remove the aysnc wrapper methods.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
