hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-3583) Coprocessors: RegionObserver: ScannerNext and ScannerClose hooks are called when get() is invoked
Date Thu, 17 Mar 2011 17:52:29 GMT

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

Ted Yu commented on HBASE-3583:
-------------------------------

Can we consider a simpler change - directly cast scanner to HRegion.RegionScanner ?
In the future, if the dependency is broken (unlikely), we can change the cast to 'instanceof'
check.

> Coprocessors: RegionObserver: ScannerNext and ScannerClose hooks are called when get()
is invoked
> -------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-3583
>                 URL: https://issues.apache.org/jira/browse/HBASE-3583
>             Project: HBase
>          Issue Type: Bug
>          Components: coprocessors
>    Affects Versions: 0.92.0
>            Reporter: Mingjie Lai
>            Assignee: Mingjie Lai
>             Fix For: 0.92.0
>
>         Attachments: HBase3583.patch
>
>
> RegionObserver upcalls are expected to be triggered by corresponding client calls. 
> I found that if a HTable.get() is issued, ScannerNext, and ScannerClose hooks are also
invoked. 
> Here is the reason: HRegion.get() is implemented with an internal scanner:
> {code}
>     InternalScanner scanner = null;
>     try {
>       scanner = getScanner(scan);
>       scanner.next(results);
>     } finally {
>       if (scanner != null)
>         scanner.close();
>     }
> {code}
> where scanner.next, and scanner.close() are implemented with RegionObserver hooks. 

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

Mime
View raw message