[
https://issues.apache.org/jira/browse/HBASE-13303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14375641#comment-14375641
]
Anoop Sam John commented on HBASE-13303:
----------------------------------------
bq.I'm not sure if it is a problem if the client underestimates the amount of
data coming back.
I have checked. Yes you are right. The math at client side should not create
any data miss issue.
Only issue is we might not be honoring the actual max result size what user
specified. Especially when the tags are returned back. The client side will
have to keep more data size and server pushed it more than what is actually
expected (as per the max size limit) . It is fine as of now. When we solve
HBASE-13262 correctly we can consider this aspects also.
> 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)
