[
https://issues.apache.org/jira/browse/HBASE-27222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17571744#comment-17571744
]
Hudson commented on HBASE-27222:
--------------------------------
Results for branch branch-2
[build #602 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/602/]:
(/) *{color:green}+1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/602/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/602/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/602/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/602/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> 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)
