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

Hadoop QA commented on HBASE-11936:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12668167/HBASE_11936_0.98.patch
  against trunk revision .
  ATTACHMENT ID: 12668167

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/10848//console

This message is automatically generated.

> IsolationLevel must be attribute of a Query not a Scan
> ------------------------------------------------------
>
>                 Key: HBASE-11936
>                 URL: https://issues.apache.org/jira/browse/HBASE-11936
>             Project: HBase
>          Issue Type: Bug
>          Components: Client
>    Affects Versions: 0.98.6
>            Reporter: Vladimir Rodionov
>            Assignee: Vladimir Rodionov
>              Labels: features
>             Fix For: 2.0.0, 0.98.7, 0.99.1
>
>         Attachments: HBASE_11936.patch, HBASE_11936_0.98.patch, 
> HBASE_11936_1.patch, HBASE_11936_2.patch
>
>
> The Get operation is implemented in HBase as a Scan. The default isolation 
> level for Scan is READ_COMMITTED. The API to change the isolation level is 
> part of Scan class and there is no way for Get operation to change this from 
> default. We should move this API up to Query (which is a parent of both: Scan 
> and Get). 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to