[
https://issues.apache.org/jira/browse/HBASE-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13856637#comment-13856637
]
Lars Hofhansl commented on HBASE-7226:
--------------------------------------
Let's also use some common sense :)
I certainly do not have to "approve" every bug fix for 0.94; nor do I want to.
Can't speak for them, but [~stack] and [~apurtell] will probably not want to do
that for each bug fix either.
For 0.94 I have been building the release directly from the svn tag (so there
is also no need to do a freeze for release purposes - of course there might be
other reasons, though).
> HRegion.checkAndMutate uses incorrect comparison result for <, <=, > and >=
> ---------------------------------------------------------------------------
>
> Key: HBASE-7226
> URL: https://issues.apache.org/jira/browse/HBASE-7226
> Project: HBase
> Issue Type: Bug
> Components: regionserver
> Reporter: Feng Honghua
> Assignee: Feng Honghua
> Fix For: 0.94.16
>
> Attachments: HBASE-7226-trunk-v2.patch, HBASE-7226-trunk.patch,
> HRegion_HBASE_7226_0.94.2.patch
>
>
> in HRegion.checkAndMutate, incorrect comparison results are used for <, <=, >
> and >=, as below:
> switch (compareOp) {
> case LESS:
> matches = compareResult <= 0; // should be '<' here
> break;
> case LESS_OR_EQUAL:
> matches = compareResult < 0; // should be '<=' here
> break;
> case EQUAL:
> matches = compareResult == 0;
> break;
> case NOT_EQUAL:
> matches = compareResult != 0;
> break;
> case GREATER_OR_EQUAL:
> matches = compareResult > 0; // should be '>=' here
> break;
> case GREATER:
> matches = compareResult >= 0; // should be '>' here
> break;
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
