I mean you need to modify Phoenix code itself to properly support such kind of features.
Thanks, Sergey On Tue, Apr 18, 2017 at 3:52 PM, Cheyenne Forbes < cheyenne.osanu.for...@gmail.com> wrote: > Could you explain a little more what you mean by that? > > Regards, > > Cheyenne O. Forbes > > > On Tue, Apr 18, 2017 at 4:36 PM, Sergey Soldatov <sergeysolda...@gmail.com > > wrote: > >> I may be wrong, but you have chosen wrong approach. Such kind of >> integration need to be (should be) done on the Phoenix layer in the way >> like global/local indexes are implemented. >> >> Thanks, >> Sergey >> >> On Tue, Apr 18, 2017 at 12:34 PM, Cheyenne Forbes < >> cheyenne.osanu.for...@gmail.com> wrote: >> >>> I am creating a plugin that uses Lucene to index text fields and I need >>> to access *getConf()* and *getFilesystem()* of *HRegion, *the Lucene >>> indexes are split with the regions so I need " *HRegion MyVar; ", *I >>> am positive the UDF will run on the region server and not the client*.* >>> >>> Regards, >>> >>> Cheyenne O. Forbes >>> >>> >>> On Tue, Apr 18, 2017 at 1:22 PM, James Taylor <jamestay...@apache.org> >>> wrote: >>> >>>> Shorter answer is "no". Your UDF may be executed on the client side as >>>> well (depending on the query) and there is of course no HRegion available >>>> from the client. >>>> >>>> On Tue, Apr 18, 2017 at 11:10 AM Sergey Soldatov < >>>> sergeysolda...@gmail.com> wrote: >>>> >>>>> Well, theoretically there is a way of having a coprocessor that will >>>>> keep static public map of current rowkey processed by Phoenix and the >>>>> correlated HRegion instance and get this HRegion using the key that is >>>>> processed by evaluate function. But it's a completely wrong approach for >>>>> both HBase and Phoenix. And it's not clear for me why SQL query may need >>>>> access to the region internals. >>>>> >>>>> Thanks, >>>>> Sergey >>>>> >>>>> On Mon, Apr 17, 2017 at 10:04 PM, Cheyenne Forbes < >>>>> cheyenne.osanu.for...@gmail.com> wrote: >>>>> >>>>>> so there is no way of getting HRegion in a UDF? >>>>>> >>>>> >>>>> >>> >> >
