You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Duo Zhang (Jira)" <ji...@apache.org> on 2022/07/26 16:16:00 UTC
[jira] [Resolved] (HBASE-27222) Purge FutureReturnValueIgnored warnings from error prone
[ https://issues.apache.org/jira/browse/HBASE-27222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Duo Zhang resolved HBASE-27222.
-------------------------------
Fix Version/s: 2.5.0
3.0.0-alpha-4
Hadoop Flags: Reviewed
Resolution: Fixed
Pushed to branch-2.5+.
Thanks [~apurtell] for reviewing!
> Purge FutureReturnValueIgnored warnings from error prone
> --------------------------------------------------------
>
> Key: HBASE-27222
> URL: https://issues.apache.org/jira/browse/HBASE-27222
> Project: HBase
> Issue Type: Improvement
> Components: netty
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 2.5.0, 3.0.0-alpha-4
>
>
> We used to introduce a FutureUtils to purge the FutureReturnValueIgnored warnings in the async client implementation, to make sure we catch the exception from the callback.
> For netty, we could apply the same trick. And there is another problem for netty that channel.write and some other methods will also return a ChannelFuture but usually we just do nothing on it, this will generated a FutureReturnValueIgnored warning too. We could add a logging listener to log the errors if any.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)