What do you mean by "have to think"? Where in the HBase codebase have you seen that?
On Dec 10, 2012, at 10:12 AM, Azury wrote: > Yes. we have to think Coprocessors are all loaded successfully if table was > configured Coprocessors if this method return true. > > > At 2012-12-10 16:01:13,"anil gupta" <[email protected]> wrote: >> Hi Asaf, >> >> Have a look at the >> *hasCoprocessor<http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/HTableDescriptor.html#hasCoprocessor%28java.lang.String%29> >> * method of HTD: >> http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/HTableDescriptor.html#hasCoprocessor(java.lang.String) >> >> It might be helpful for you. I have used it in past to check whether a >> coprocessors is successfully added or not. >> >> HTH, >> Anil >> >> On Sun, Dec 9, 2012 at 2:25 PM, Ted Yu <[email protected]> wrote: >> >>> On region server web UI, you should see the list of coprocessors loaded. >>> >>> But I guess you're looking for a programmatic way of detecting coprocessor >>> deployment. >>> >>> Cheers >>> >>> On Sun, Dec 9, 2012 at 12:29 PM, Mesika, Asaf <[email protected]> >>> wrote: >>> >>>> 0.94.0 >>>> On Dec 9, 2012, at 3:03 PM, [email protected] wrote: >>>> >>>>> Which hbase version are you targeting ? >>>>> >>>>> Thanks >>>>> >>>>> >>>>> >>>>> On Dec 9, 2012, at 2:55 AM, "Mesika, Asaf" <[email protected]> >>>> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I wrote a custom Region Observer. >>>>>> I'm currently writing an Installer class for it. >>>>>> In this installer I'm adding the region observer by adding a >>>> coprocessor to the HTableDescriptor, and then calling modifyTable by >>>> HBaseAdmin. >>>>>> >>>>>> My question is: How can I check whether region observer was loaded >>>> successfully for this table? >>>>>> >>>>>> I tried searching for a way to get the Coprocessor.State somehow for >>> my >>>> region observer so I'll know it's ACTIVE, but couldn't find a way. >>>>>> >>>>>> >>>>>> Thank you, >>>>>> >>>>>> Asaf >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>> >>>> >>> >> >> >> >> -- >> Thanks & Regards, >> Anil Gupta
