[
https://issues.apache.org/jira/browse/HBASE-10096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13842955#comment-13842955
]
Anoop Sam John commented on HBASE-10096:
----------------------------------------
Will this change be compatible with older 94 point releases? An old client and
new version of RS?
My bad, I have not done this the 1st time. It was better for 0.94. In 96 and
above any way we have PB based response.
> make BulkDeleteResponse implement Writable to reduce the transfer size for rpc
> ------------------------------------------------------------------------------
>
> Key: HBASE-10096
> URL: https://issues.apache.org/jira/browse/HBASE-10096
> Project: HBase
> Issue Type: Improvement
> Components: Coprocessors, Performance
> Reporter: cuijianwei
> Attachments: HBASE-10096-0.94-v1.patch
>
>
> As [https://issues.apache.org/jira/browse/HBASE-6942] introduced,
> BulkDeleteEndpoint provides 'delete' method which performs like sql : "delete
> from table where ...". BulkDeleteEndpoint is efficient because it can
> complete scan and delete in one rpc and also could be implemented parallelly
> in different regions using coprocessor. BulkDeleteResponse is represents the
> result of BulkDeleteEndpoint.delete and will be serialized using a standard
> java serializable way. However, the serialized length of BulkDeleteResponse
> will be longer than one hundred byte length and may be not efficient enough
> to pass on the network. Therefore, is it better to make BulkDeleteResponse
> implement Writable interface and provide more efficient serialize method?
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
