[
https://issues.apache.org/jira/browse/HBASE-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119741#comment-13119741
]
Hudson commented on HBASE-4334:
-------------------------------
Integrated in HBase-0.92 #41 (See
[https://builds.apache.org/job/HBase-0.92/41/])
HBASE-4334 HRegion.get never validates row (Lars H)
tedyu :
Files :
* /hbase/branches/0.92/CHANGES.txt
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
*
/hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java
> HRegion.get never validates row
> -------------------------------
>
> Key: HBASE-4334
> URL: https://issues.apache.org/jira/browse/HBASE-4334
> Project: HBase
> Issue Type: Bug
> Components: regionserver
> Affects Versions: 0.90.4
> Reporter: Joe Pallas
> Assignee: Lars Hofhansl
> Fix For: 0.92.0
>
> Attachments: 4334-v2.txt, 4334-v3.txt, 4334.txt
>
>
> If a client gets confused (possibly by a hole in .META., see HBASE-4333), it
> may send a request to the wrong region. Paths through put, delete,
> incrementColumnValue, and checkAndMutate all call checkRow either directly or
> indirectly (through getLock). But get apparently does not. This can result
> in returning an incorrect empty result instead of a WrongRegionException.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
