[
https://issues.apache.org/jira/browse/HBASE-4784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150763#comment-13150763
]
Hudson commented on HBASE-4784:
-------------------------------
Integrated in HBase-TRUNK #2443 (See
[https://builds.apache.org/job/HBase-TRUNK/2443/])
HBASE-4784 Handle void return types in CoprocessorProtocol methods
garyh :
Files :
* /hbase/trunk/CHANGES.txt
*
/hbase/trunk/src/main/java/org/apache/hadoop/hbase/client/coprocessor/ExecResult.java
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
*
/hbase/trunk/src/test/java/org/apache/hadoop/hbase/regionserver/TestServerCustomProtocol.java
> Void return types not handled correctly for CoprocessorProtocol methods
> -----------------------------------------------------------------------
>
> Key: HBASE-4784
> URL: https://issues.apache.org/jira/browse/HBASE-4784
> Project: HBase
> Issue Type: Bug
> Components: coprocessors
> Affects Versions: 0.92.0, 0.94.0
> Reporter: Gary Helmling
> Assignee: Gary Helmling
> Priority: Critical
> Fix For: 0.92.0
>
> Attachments: HBASE-4784.patch
>
>
> If a CoprocessorProtocol derived interface defines a method with a void
> return type, the method cannot be called using HTable.coprocessorExec().
> Instead ExecResult will throw an IOException on the client trying to do a
> Class.forName() on "void".
> Looking at ExecResult, it appears that the valueType field (which causes the
> error) is no longer even used, so I'd suggest we just get rid of it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
