[
https://issues.apache.org/jira/browse/HBASE-13303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14375437#comment-14375437
]
Andrew Purtell commented on HBASE-13303:
----------------------------------------
As you can see from the unit test in this patch, we definitely have issues if
the server estimates a larger size that the client, which will happen if we
include tags in the sizing.
I'm not sure if it is a problem if the client underestimates the amount of data
coming back. I will have to look at the code when next at my desk.
We could have the server estimate with tag size included if the user is a
superuser, but then this graduates from a hack to a really ugly layering
violation.
Since you've pointed out what you think is a problem maybe you have a
suggestion to solve it Anoop?
> Fix size calculation of results on the region server
> ----------------------------------------------------
>
> Key: HBASE-13303
> URL: https://issues.apache.org/jira/browse/HBASE-13303
> Project: HBase
> Issue Type: Sub-task
> Components: Client
> Reporter: Lars Hofhansl
> Assignee: Andrew Purtell
> Fix For: 2.0.0, 1.0.1, 1.1.0, 0.98.12
>
> Attachments: HBASE-13303-0.98.patch, HBASE-13303-0.98.patch,
> HBASE-13303-0.98.patch, HBASE-13303.patch, HBASE-13303.patch,
> HBASE-13303.patch, TestResultSizeEstimation.java
>
>
> One of the problems in the parent is due to different size calculation
> between client and server when HFilev3 is used.
> Since tags are _never_ shipped to the client in a scan, we can have special
> size function (or a flag on the current one) that does not include the tags
> and the tags meta information (the length is what causes the issue), so that
> client and server will always calculate the same size.
> I'll make a patch within the hour, unless somebody beats me to it.
> [~apurtell], FYI.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
