[
https://issues.apache.org/jira/browse/HBASE-21715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16751193#comment-16751193
]
Hudson commented on HBASE-21715:
--------------------------------
Results for branch branch-2.0
[build #1284 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/1284/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/1284//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/1284//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/1284//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> Do not throw UnsupportedOperationException in ProcedureFuture.get
> -----------------------------------------------------------------
>
> Key: HBASE-21715
> URL: https://issues.apache.org/jira/browse/HBASE-21715
> Project: HBase
> Issue Type: Task
> Components: Client
> Reporter: Duo Zhang
> Assignee: Junhong Xu
> Priority: Major
> Fix For: 3.0.0, 2.2.0, 2.1.3, 2.0.5
>
> Attachments: HBase-21715.v01.patch, HBase-21715.v03.patch
>
>
> This is really a bad practice, no one would expected that a Future does not
> support get, and this can not be detected at compile time. Even though we do
> not want user to wait for ever, we could set a long timeout, for example, 10
> minutes,instead of throwing UnsuportedOperationException. I've already been
> hurt many times...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
