[
https://issues.apache.org/jira/browse/HBASE-7238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13554539#comment-13554539
]
Sergey Shelukhin commented on HBASE-7238:
-----------------------------------------
I poked around protobuf code. Do we want the wire size of Result-s, in
particular?
Getting that out of the protobuf doesn't look possible via normal interfaces.
We can call getSerializedSize on each Result but that may be expensive. We can
also call getSerializedSize on them on server side, before adding them to
response, and store that inside response too (one long per response);
getSerializedSize is memoized on first call, it's called recursively on nested
structures, and called during message serialization in RPC (and during write by
protobuf), this call is made anyway and thus should not impact perf.
> Size based scan metric broken by protobufs
> ------------------------------------------
>
> Key: HBASE-7238
> URL: https://issues.apache.org/jira/browse/HBASE-7238
> Project: HBase
> Issue Type: Sub-task
> Reporter: Lars Hofhansl
> Priority: Critical
> Fix For: 0.96.0
>
>
> See ScannerCallable. HBASE-7215 comments that portion, but it did not work
> before, because Results.bytes is no longer used with protobufs.
--
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
