[CRUNCH-546] Avoid CellUtil.cloneXXX in HFileUtils and HFileInputFormat

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.13.0
• Assignee: Gabriel Reid
• Reporter: Gabriel Reid
• Created: 19/Jul/15 14:41
• Updated: 06/Aug/15 04:39
• Resolved: 20/Jul/15 13:27

Description

HFileUtils and HFileInputFormat currently make use of the CellUtil.cloneXXX in a number of places when comparing row, family, and qualifier values with a constant.

The clone methods are relatively costly, as they require allocating a new byte array and copying all data over into the new array on every call.

Bytes.equals, Bytes.compareTo, and ByteBuffer.wrap also accept a byte array and offset and length parameters, which allows accessing portions of KeyValues without copying them out into a separate byte array when using them for comparison. We should replace the uses of CellUtil.cloneXXX with the alternate calls to the above methods where possible.