[ https://issues.apache.org/jira/browse/HBASE-20656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16493422#comment-16493422 ]
Balazs Meszaros edited comment on HBASE-20656 at 5/29/18 11:36 AM: ------------------------------------------------------------------- [~mdrob] sorry, I don't understand it. The package of WALEdit has been changed. How can I write a code, which depends on the old package? I solved it by adding a jar, another solution would be byte-code generation. I have no other idea. (I will fix the build issues later.) was (Author: balazs.meszaros): [~mdrob] sorry, I don't understand it. The package of WALEdit has been changed. How can I write a code, which depends on the old package? I solved it by adding a jar, another solution would be byte-code generation. I have no other idea. > 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, > HBASE-20656.master.002.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)