You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by Nick Dimiduk <nd...@apache.org> on 2016/12/11 01:43:02 UTC
HBase RpcServerInterface changes from HBASE-16033
Heya,
In reviewing changes for the next HBase 1.1 release, I noticed that
HBASE-16033 introduces a new method to o.a.h.h.ipc.RpcServerInterface. This
class is marked as LimitedPrivate(Phoenix). I'm not seeing any references
to that class name in the Phoenix code on any of the 1.1 branches, but I
wanted to double-check with folks here before writing it off.
Will introduction of a new method break some implementation we have over
here?
Thanks a lot,
Nick
Re: HBase RpcServerInterface changes from HBASE-16033
Posted by Nick Dimiduk <nd...@gmail.com>.
Okay thanks James!
On Mon, Dec 12, 2016 at 4:33 PM, James Taylor <ja...@apache.org>
wrote:
> Hey Nick,
> Adding new methods won't cause a problem, but thanks for asking.
>
> James
>
> On Sat, Dec 10, 2016 at 5:43 PM, Nick Dimiduk <nd...@apache.org> wrote:
>
> > Heya,
> >
> > In reviewing changes for the next HBase 1.1 release, I noticed that
> > HBASE-16033 introduces a new method to o.a.h.h.ipc.RpcServerInterface.
> > This
> > class is marked as LimitedPrivate(Phoenix). I'm not seeing any references
> > to that class name in the Phoenix code on any of the 1.1 branches, but I
> > wanted to double-check with folks here before writing it off.
> >
> > Will introduction of a new method break some implementation we have over
> > here?
> >
> > Thanks a lot,
> > Nick
> >
>
Re: HBase RpcServerInterface changes from HBASE-16033
Posted by James Taylor <ja...@apache.org>.
Hey Nick,
Adding new methods won't cause a problem, but thanks for asking.
James
On Sat, Dec 10, 2016 at 5:43 PM, Nick Dimiduk <nd...@apache.org> wrote:
> Heya,
>
> In reviewing changes for the next HBase 1.1 release, I noticed that
> HBASE-16033 introduces a new method to o.a.h.h.ipc.RpcServerInterface.
> This
> class is marked as LimitedPrivate(Phoenix). I'm not seeing any references
> to that class name in the Phoenix code on any of the 1.1 branches, but I
> wanted to double-check with folks here before writing it off.
>
> Will introduction of a new method break some implementation we have over
> here?
>
> Thanks a lot,
> Nick
>