[
https://issues.apache.org/jira/browse/HBASE-16264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-16264:
--------------------------
Release Note: Shade/relocate the protobuf hbase uses internally. Even
though our API references protobufs -- to support Coprocessor Endpoints --
Coprocessor Endpoints should still work (it is a bug if they do not). (was:
Shade/relocate the protobuf hbase uses internally. Even though our API
references protobufs -- to support Coprocessor Endpoints -- Coprocessor
Endpoints should still work (it is a bug if they do not).
Downside for developers is that you will have to add a built version of the
hbase-protocol jar -- the module that includes the shaded protobuf -- to your
IDE build path so the relocated protobufs can be resolved.)
> 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
>
>
> 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
(v6.3.4#6332)
