Some unit tests in HBase show how you can install test coprocessors that do
various broken things. If you install it so it sorts below the Phoenix
coprocessors in priority then at runtime the Phoenix coprocessor code will
be called by the coprocessor framework, Phoenix code will do whatever and
han
As I mentioned above, not off the top of my head :-/ but I was just using
simple region observers - all you need to do is add them to the list for
the config before cluster start up and should be good to go.
On Mon, Feb 9, 2015, 1:03 PM Eli Levine wrote:
> Thanks, Jesse. Very useful. Any pointer
Thanks, Jesse. Very useful. Any pointers to specific tests that spin up
Coprocessors dynamically in Phoenix?
On Mon, Feb 9, 2015 at 11:51 AM, Jesse Yates
wrote:
> Yeah, I've done that a handful of times in HBase-land (not sure where
> though). It gets tricky with phoenix using all the BaseTest s
Yeah, I've done that a handful of times in HBase-land (not sure where
though). It gets tricky with phoenix using all the BaseTest stuff because
it does a lot of setup things that could conflict with what you are trying
to do.*
What I was frequently doing was using a static "latch" for turning on/o
Greetings Phoenix devs,
I'm working on https://issues.apache.org/jira/browse/PHOENIX-900 (Partial
results for mutations). In order to test this functionality properly, I
need to write one or more tests that simulate write failures in HBase.
I think this will involve having a test deploy a custom
