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 hand control back to HBase by returning, the coprocessor framework will then call the test coprocessor which will simulate failure, and I think this is the ordering you want.
On Mon, Feb 9, 2015 at 11:01 AM, Eli Levine <elilev...@gmail.com> wrote: > 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 test-only > coprocessor that will cause some predefined writes to fail, which the test > will verify. Does that sound like the right approach? Any examples of > similar tests in Phoenix or anywhere else in HBase-land? > > Thanks, > > Eli > -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
