[
https://issues.apache.org/jira/browse/HBASE-14524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14989470#comment-14989470
]
Lars Francke commented on HBASE-14524:
--------------------------------------
[~anoop.hbase] I didn't get around to it and it can be another few weeks or
months, I'm swamped at the moment. Found this when debugging the read path for
a customer and was surprised that for every new row those two values are the
same. I have it on my radar though and will update here when I get around to it.
> Short-circuit comparison of rows in CellComparator
> --------------------------------------------------
>
> Key: HBASE-14524
> URL: https://issues.apache.org/jira/browse/HBASE-14524
> Project: HBase
> Issue Type: Improvement
> Reporter: Lars Francke
> Assignee: Lars Francke
> Priority: Minor
> Attachments: 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)
