[ https://issues.apache.org/jira/browse/HBASE-20656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16492773#comment-16492773 ]
Mike Drob commented on HBASE-20656: ----------------------------------- I don't like having binary blob in our source tree, even for test data purposes. Would be better to have a src file that has whatever methods it needs to simulate being an HBase1 coprocessor and check that instead. We might not get jar coverage, but that's probably ok? > 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 > Attachments: HBASE-20656.master.001.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)