White)
- Original Message -
> From: lars hofhansl
> To: "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
e.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 extens
> 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 rega
che.org"
Sent: Thursday, January 26, 2012 10:58 AM
Subject: Re: Difference between coprocessors and filters
Praveen,
> What are the differences between filters and coprocessors leaving
> aside the code/API?
I don't think one can leave aside the API ...
Filters came first. They were a
- Andy
Problems worthy of attack prove their worth by hitting back. - Piet Hein (via
Tom White)
From: Praveen Sripati
To: user@hbase.apache.org
Sent: Wednesday, January 25, 2012 10:24 PM
Subject: Difference between coprocessors and filters
Hi,
Co
h by hitting back. - Piet Hein (via
Tom White)
>
> From: Praveen Sripati
>To: user@hbase.apache.org
>Sent: Wednesday, January 25, 2012 10:24 PM
>Subject: Difference between coprocessors and filters
>
>Hi,
>
>Coprocessors introd
Hi,
Coprocessors introduced in 0.92 can also be used to filter out the data
similar to the filters. What are the differences between filters and
coprocessors leaving aside the code/API? One thing I can think is, filters
are defined at the client, while the coprocessors are defined on the
server. S
