hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-11936) IsolationLevel must be attribute of a Query not a Scan
Date Wed, 10 Sep 2014 22:11:34 GMT

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

Andrew Purtell commented on HBASE-11936:


This says moving a method upward in the class hierarchy is fine: http://docs.oracle.com/javase/specs/jls/se7/html/jls-13.html

This much older one - http://www.cs.cornell.edu/andru/javaspec/13.doc.html - says the same
but additionally "provided a forwarding method is left in its place". 

I'm not an expert on Java binary compatibility.

> 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
> 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

View raw message