stack commented on HBASE-16264:

Tactic #4 seems to work: i.e. a copy of hbase-protocol relocated as 
hbase-protocol-shaded and then move all of core -- all but the Coprocessor 
Endpoints -- to refer to the relocated content of hbase-protocol-shaded. See 
doc. for TODOs still and some interesting issues uncovered here that can be 
dealt with in a follow-on (patch is big enough as it is). Downsides -- awkward 
in the IDE, extra copy when doing CPEPs -- each look addressable. Posting 
current patch here now it compiles and seems to pass tests. Will work on some 
of the TODOs and what ever hadoopqa turns up next.

> Figure how to deal with endpoints and shaded pb
> -----------------------------------------------
>                 Key: HBASE-16264
>                 URL: https://issues.apache.org/jira/browse/HBASE-16264
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Coprocessors, Protobufs
>            Reporter: stack
>            Assignee: stack
>            Priority: Critical
>             Fix For: 2.0.0
>         Attachments: 16264.tactic2.patch, HBASE-16264.master.001.patch, 
> HBASE-16264.master.002.patch, HBASE-16264.master.003.patch, 
> HBASE-16264.master.004.patch, HBASE-16264.master.005.patch, 
> HBASE-16264.master.006.patch, HBASE-16264.master.007.patch, 
> HBASE-16264.master.008.patch
> Come up w/ a migration plan for coprocessor endpoints when our pb is shaded. 
> Would be sweet if could make it so all just worked. At worst, come up w/ a 
> prescription for how to migrate existing CPs.

This message was sent by Atlassian JIRA

Reply via email to