[
https://issues.apache.org/jira/browse/HBASE-16444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15432691#comment-15432691
]
Hudson commented on HBASE-16444:
--------------------------------
FAILURE: Integrated in Jenkins build HBase-1.4 #361 (See
[https://builds.apache.org/job/HBase-1.4/361/])
HBASE-16444 CellUtil#estimatedSerializedSizeOfKey() should consider
(ramkrishna: rev e7cd7fffbf4b297e54438c1378f0b9aa2c98523b)
* (edit) hbase-common/src/main/java/org/apache/hadoop/hbase/CellUtil.java
> CellUtil#estimatedSerializedSizeOfKey() should consider
> KEY_INFRASTRUCTURE_SIZE
> -------------------------------------------------------------------------------
>
> Key: HBASE-16444
> URL: https://issues.apache.org/jira/browse/HBASE-16444
> Project: HBase
> Issue Type: Bug
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
> Priority: Minor
> Fix For: 2.0.0, 1.4.0
>
> Attachments: HBASE-16444.patch, HBASE-16444_1.patch,
> HBASE-16444_2.patch
>
>
> Currently CellUtil#getSumOfCellKeyElementLengths() considers
> {code}
> return cell.getRowLength() + cell.getFamilyLength() +
> cell.getQualifierLength() +
> KeyValue.TIMESTAMP_TYPE_SIZE;
> {code}
> It can consider the 2 byte ROWLEN and 1 byte FAMILY_LEN also because with the
> current way of things we are sure how our key is structured.
> But pls note that
> {code}
> // This will be a low estimate. Will do for now.
> return getSumOfCellKeyElementLengths(cell);
> {code}
> It says clearly it is going to be a low estimate. But in the write path there
> should be no harm in adding the complete KEY_INFRA_SIZE.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
