hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Purtell <apurt...@apache.org>
Subject Re: Difference between coprocessors and filters
Date Mon, 30 Jan 2012 02:37:05 GMT
Right, I wasn't thinking of a replacement, just that this seems like missing information that
is available at the callout location that should be passed through. 
 
Best regards,

     - Andy

Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White) 


----- Original Message -----
> From: lars hofhansl <lhofhansl@yahoo.com>
> To: "user@hbase.apache.org" <user@hbase.apache.org>
> Cc: 
> Sent: Sunday, January 29, 2012 3:23 PM
> Subject: Re: Difference between coprocessors and filters
> 
> Sure. Although I am not sure whether coprocessors should actually do that. They 
> can operate on top of a scanner that is already filtered by a filter.
> I think that would need a completely new API.
> 
> 
> -- Lars
> 
> 
> ________________________________
> From: Andrew Purtell <apurtell@yahoo.com>
> To: "user@hbase.apache.org" <user@hbase.apache.org> 
> Sent: Sunday, January 29, 2012 11:09 AM
> Subject: Re: Difference between coprocessors and filters
> 
>>  Seek-hints could be added to coprocessors - preScannerNext/postScannerNext 
> -, but they do not currently support this.)
> 
> Coprocessors shouldn't be a catch-all for every extension case, but this is 
> arguably missing information that should be passed through. File a JIRA for it 
> Lars? 
> 
> Best regards,
> 
>     - Andy
> 
> 
> On Jan 28, 2012, at 8:53 PM, lars hofhansl <lhofhansl@yahoo.com> wrote:
> 
>>  Seek-hints could be added to coprocessors - preScannerNext/postScannerNext 
> -, but they do not currently support this.)
> 

Mime
View raw message