[
https://issues.apache.org/jira/browse/HBASE-16264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15533292#comment-15533292
]
stack commented on HBASE-16264:
-------------------------------
New patch adds a hbase-endpoint module and moves all the bundled CPEPs to it,
those that are non-core; i.e. bulk loading, aggregation, etc. This moves a
bunch of code out of hbase-server module. Also moved the protos that are scoped
to a module back to the module so rest now gets its protos back and so does
rsgroup. This underlines the point we are trying to make about the difference
between internal protobuf and external.
Uploaded to review board a patch that is minus the generated files.
> 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-Figure-how-to-deal-with-endpoints-and-sh.master.013.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,
> HBASE-16264.master.009.patch, HBASE-16264.master.010.patch,
> HBASE-16264.master.011.patch, HBASE-16264.master.012.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)
