Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 2 Feb 2011 07:53:28 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <2000227507.4599.1296633208996.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <274797635.657.1296510089836.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Commented: (HBASE-3494) checkAndPut implementation doesnt
 verify row param and writable row are the same
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-3494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12989546#comment-12989546 ] 

Hudson commented on HBASE-3494:
-------------------------------

Integrated in HBase-TRUNK #1728 (See [https://hudson.apache.org/hudson/job/HBase-TRUNK/1728/])
    

> checkAndPut implementation doesnt verify row param and writable row are the same
> --------------------------------------------------------------------------------
>
>                 Key: HBASE-3494
>                 URL: https://issues.apache.org/jira/browse/HBASE-3494
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.90.0
>            Reporter: ryan rawson
>            Assignee: ryan rawson
>             Fix For: 0.90.1
>
>         Attachments: HBASE-3494.txt
>
>
> the API checkAndPut, and on the server side checkAndMutate doesn't enforce that the row in the API call and the row in the passed writable that should be executed if the check passes, are the same row!  Looking at the code, if someone were to 'fool' us, we'd probably end up with rows in the wrong region in the worst case.  Or we'd end up with non-locked puts/deletes to different rows since the checkAndMutate grabs the row lock and calls put/delete methods that do not grab row locks.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira