hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj Das (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-6785) Convert AggregateProtocol to protobuf defined coprocessor service
Date Mon, 01 Oct 2012 22:27:07 GMT

     [ https://issues.apache.org/jira/browse/HBASE-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Devaraj Das updated HBASE-6785:

    Attachment: Aggregate.proto

Attaching a first pass on the PB definition. 

I made the return type of the aggregation RPC response as one of the primitive types. Also,
left a placeholder 'bytes' for the ColumnInterpreter serialization if someone wants to pass
interpreter specific data to the server (LongColumnInterpreter doesn't need to serialize anything).

Unfortunately, I think users will be impacted w.r.t the usage (via AggregationClient) - for
example, the ColumnInterpreter will have to extend PB's Message (as opposed to Writable that
it currently extends).

Does the approach look okay?
> Convert AggregateProtocol to protobuf defined coprocessor service
> -----------------------------------------------------------------
>                 Key: HBASE-6785
>                 URL: https://issues.apache.org/jira/browse/HBASE-6785
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Coprocessors
>            Reporter: Gary Helmling
>            Assignee: Devaraj Das
>             Fix For: 0.96.0
>         Attachments: Aggregate.proto
> With coprocessor endpoints now exposed as protobuf defined services, we should convert
over all of our built-in endpoints to PB services.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message