hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-3494) checkAndPut implementation doesnt verify row param and writable row are the same
Date Wed, 02 Feb 2011 20:12:28 GMT

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

stack commented on HBASE-3494:
------------------------------

@Joe Agreed

> 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

        

Mime
View raw message