You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by amir <as...@akamai.com> on 2012/06/03 16:30:16 UTC

Coprocessor

hi

I am new to Hbase Coprocessor.
After doing some reading and code inspection its look like there is no way
to stream the coprocessor results to the client during coprocessor run on
the region server.

Am i missing something here?

I may need to process TB in each region server, if the client will have to
wait till start getting results for a coprocessor to end its run, it may be
very inefficient more over the results size may be huge and holding all of
them in the memory either on the region server or in the client may cause
one of them to crush - the result must then be stream base.

Thanks

--
View this message in context: http://apache-hbase.679495.n3.nabble.com/Coprocessor-tp4018772.html
Sent from the HBase - Developer mailing list archive at Nabble.com.

RE: Coprocessor

Posted by Vladimir Rodionov <vr...@carrieriq.com>.
I think the combination of a Scanner on a client side  and Coprocessor (RegionObserver) on HBase side will provide
streaming functionality you need.

Your coprocessor can intercept all scanner operations (preScannerOpen, postScannerOpen, preScannerClose, postScannerClose, preScannerNext, postScannerNext)
and you can add your logic on these hooks.

Best regards,
Vladimir Rodionov
Principal Platform Engineer
Carrier IQ, www.carrieriq.com
e-mail: vrodionov@carrieriq.com

________________________________________
From: amir [askovron@akamai.com]
Sent: Sunday, June 03, 2012 7:30 AM
To: hbase-dev@hadoop.apache.org
Subject: Coprocessor

hi

I am new to Hbase Coprocessor.
After doing some reading and code inspection its look like there is no way
to stream the coprocessor results to the client during coprocessor run on
the region server.

Am i missing something here?

I may need to process TB in each region server, if the client will have to
wait till start getting results for a coprocessor to end its run, it may be
very inefficient more over the results size may be huge and holding all of
them in the memory either on the region server or in the client may cause
one of them to crush - the result must then be stream base.

Thanks

--
View this message in context: http://apache-hbase.679495.n3.nabble.com/Coprocessor-tp4018772.html
Sent from the HBase - Developer mailing list archive at Nabble.com.

Confidentiality Notice:  The information contained in this message, including any attachments hereto, may be confidential and is intended to be read only by the individual or entity to whom this message is addressed. If the reader of this message is not the intended recipient or an agent or designee of the intended recipient, please note that any review, use, disclosure or distribution of this message or its attachments, in any form, is strictly prohibited.  If you have received this message in error, please immediately notify the sender and/or Notifications@carrieriq.com and delete or destroy any copy of this message and its attachments.