[
https://issues.apache.org/jira/browse/HBASE-6787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13497562#comment-13497562
]
Devaraj Das commented on HBASE-6787:
------------------------------------
bq. between this and the ColumnInterpreter stuff for AggregateService, we seem
to be working towards a common interface for the user code
serialization/deserialization bits
Yeah.. that's true. Should we move this work to a different jira (where we make
the relevant changes for the other coprocessor implementations as well).
bq. But I think we're adding some complexity to remain serialization agnostic
in this case. Is the need there to make the trade off worth it?
I am not sure if we should enforce PB for users to be able to use the
coprocessor service, but I can go either way, and yeah doing pure PB everywhere
(in framework & user code) would probably make the implementation of the
framework code simpler. Will take a pass at it...
> Convert RowProcessorProtocol to protocol buffer service
> -------------------------------------------------------
>
> Key: HBASE-6787
> URL: https://issues.apache.org/jira/browse/HBASE-6787
> Project: HBase
> Issue Type: Sub-task
> Components: Coprocessors
> Reporter: Gary Helmling
> Assignee: Devaraj Das
> Fix For: 0.96.0
>
> Attachments: 6787-1.patch, 6787-2.patch
>
>
> 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
