[
https://issues.apache.org/jira/browse/HBASE-13537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14517302#comment-14517302
]
Matteo Bertozzi commented on HBASE-13537:
-----------------------------------------
from the semantic versioning discussion -
http://hbase.apache.org/book.html#hbase.versioning
MAJOR.MINOR.PATCH
MAJOR version when you make incompatible API changes
Client Binary compatibility:
Client code written to APIs available in a given PATCH RELEASE can run
unchanged (no recompilation needed) against the new jars of later patch
versions.
so, in 2.0 we can break binary compatibility and also make incompatible API
changes.
in this case we are just changing a return type which causes binary
compatibility, but nothing else. your code can still work even ignoring the
return value. you just need to recompile
> 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)
