Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
HBase >> mail # dev >> [pre,post]ScannerOpen() returning a custom RegionScanner implementation


Copy link to this message
-
RE: [pre,post]ScannerOpen() returning a custom RegionScanner implementation
Ted,

You can see this comment from Andrew
https://issues.apache.org/jira/browse/HBASE-5517?focusedCommentId=13225624&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13225624

-Anoop-

________________________________________
From: lars hofhansl [[EMAIL PROTECTED]]
Sent: Saturday, June 02, 2012 8:18 PM
To: [EMAIL PROTECTED]
Subject: Re: [pre,post]ScannerOpen() returning a custom RegionScanner implementation

In general I think it would be beneficial if a Coprocessor could interfere with the sequence number logic.
The problem is that it would constitute an API change.

-- Lars

________________________________
 From: Ted Yu <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: Saturday, June 2, 2012 7:40 AM
Subject: [pre,post]ScannerOpen() returning a custom RegionScanner implementation

Hi,
In reviewing HBASE-5974, Anoop brought up the following consideration (
https://issues.apache.org/jira/browse/HBASE-5974?focusedCommentId=13285365&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13285365
):

Why I was not doing that because through the CP we have exposed the
RegionScanner interface. The pre and post scannerOpen methods in the CP can
return an impl for the RegionScanner now. So in that case customer need to
worry abt maintain this seqNo? I felt that wont be good.

If anyone utilizes [pre,post]ScannerOpen() to return a custom RegionScanner
implementation, would you please share your use case ?

Thanks