[
https://issues.apache.org/jira/browse/HBASE-15793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15275543#comment-15275543
]
Jurriaan Mous commented on HBASE-15793:
---------------------------------------
What do we do about the findbugs issue?
The class name org.apache.hadoop.hbase.client.Future shadows the simple name of
implemented interface io.netty.util.concurrent.Future
Bug type NM_SAME_SIMPLE_NAME_AS_INTERFACE (click for details)
In class org.apache.hadoop.hbase.client.Future
In class io.netty.util.concurrent.Future
In Future.java
Well the Netty future also extends java Future. But now we have this constant
Findbugs warning with each Hadoop QA run.
> Port over AsyncCall improvements
> ---------------------------------
>
> Key: HBASE-15793
> URL: https://issues.apache.org/jira/browse/HBASE-15793
> Project: HBase
> Issue Type: Improvement
> Components: rpc
> Reporter: Jurriaan Mous
> Assignee: Jurriaan Mous
> Fix For: 2.0.0
>
> Attachments: HBASE-15793-v1.patch, HBASE-15793.patch
>
>
> Again a part of HBASE-13784 patch.
> This issue is about porting over the improvements in AsyncCall so it is a
> more flexible for usage in true async calls. It will not depend anymore on
> PayloadCarryingRpcController which is not needed in the async implementation.
> Furthermore it introduces the MessageConverter and IOExceptionConverter so
> the responses of future async calls can be converted in an easy async way.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
