hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4784) Void return types not handled correctly for CoprocessorProtocol methods
Date Tue, 15 Nov 2011 02:04:52 GMT

    [ https://issues.apache.org/jira/browse/HBASE-4784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150169#comment-13150169

Lars Hofhansl commented on HBASE-4784:

+1 on patch

Nice how valueType is happily serialized and deserialized over the wire but not actually used
anywhere :)
> 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


View raw message