Re: Seeking feedback on severity of change to hbase coprocessor api from phoenix community.

2017-03-06 Thread James Taylor
Yes, thanks for asking, Sean. One way you can test this is to apply your patch locally, have Phoenix point to your new local version, and the just run our unit test suite with "mvn verify". James On Mon, Mar 6, 2017 at 3:26 PM, Josh Elser wrote: > Hey Sean, > > Thanks for taking a moment to

Re: Seeking feedback on severity of change to hbase coprocessor api from phoenix community.

2017-03-06 Thread Josh Elser
Hey Sean, Thanks for taking a moment to ask! I did a quick grep over some branches for `RpcServerInterface` and I don't see any usages. The only thing I could find (and, that I was aware of) was some use of the RpcScheduler classes. It doesn't seem like this change would cause any heartburn.

Seeking feedback on severity of change to hbase coprocessor api from phoenix community.

2017-03-04 Thread Sean Busbey
Hi Folks! If someone could take a look at HBASE-17725, I'd appreciate it. short version: The RpcServiceInterface API has added a method. That interface is marked as IA.LimitedPrivate for Coprocessors generally and Phoenix specifically. The change is already in two HBase 1.1 releases, but 1.2.5