[
https://issues.apache.org/jira/browse/HBASE-14524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15082565#comment-15082565
]
Hudson commented on HBASE-14524:
--------------------------------
FAILURE: Integrated in HBase-Trunk_matrix #610 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/610/])
HBASE-14524 Short-circuit comparison of rows in CellComparator. (Lars
(anoopsamjohn: rev 9997e4ee52136a681faa825dea46bd1162d71eca)
* hbase-common/src/main/java/org/apache/hadoop/hbase/CellComparator.java
> Short-circuit comparison of rows in CellComparator
> --------------------------------------------------
>
> Key: HBASE-14524
> URL: https://issues.apache.org/jira/browse/HBASE-14524
> Project: HBase
> Issue Type: Improvement
> Components: Performance, Scanners
> Reporter: Lars Francke
> Assignee: Lars Francke
> Fix For: 2.0.0
>
> Attachments: HBASE-14524.patch, HBASE-14524.patch, HBASE-14524.patch
>
>
> {{CellComparator#compareRows}} compares two rows. For Scans and Gets these
> objects can sometimes be exactly the same object.
> I see this (without fully understanding everything that's going on) for the
> first cell in each row.
> In these circumstances I think it makes sense to short-circuit the comparison
> (not do a byte comparison and class cast checks) and bail out early if the
> objects are identical.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
