[
https://issues.apache.org/jira/browse/HBASE-20656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16508221#comment-16508221
]
Mike Drob commented on HBASE-20656:
-----------------------------------
Fixed checkstyle on commit, pushed to branch-2.0+ (fyi [~stack])
> Validate pre-2.0 coprocessors against HBase 2.0+
> ------------------------------------------------
>
> Key: HBASE-20656
> URL: https://issues.apache.org/jira/browse/HBASE-20656
> Project: HBase
> Issue Type: New Feature
> Components: tooling
> Affects Versions: 3.0.0
> Reporter: Balazs Meszaros
> Assignee: Balazs Meszaros
> Priority: Major
> Fix For: 3.0.0, 2.1.0, 2.0.1
>
> Attachments: HBASE-20656.master.001.patch,
> HBASE-20656.master.002.patch, HBASE-20656.master.003.patch,
> HBASE-20656.master.004.patch, HBASE-20656.master.005.patch,
> HBASE-20656.master.006.patch, HBASE-20656.master.007.patch,
> HBASE-20656.master.008.patch
>
>
> We have co-processors for a while, but the API has been changed recently. We
> should give some tooling for our users to determine if they can use the
> previous co-processors safely or not.
> The tool should:
> - try to load the co-processors on our current classpath for ensuring class
> references are on our classpath,
> - should check for previously removed co-processor methods.
> In this version we check only method signatures. Code references should be
> checked in further versions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
