[ 
https://issues.apache.org/jira/browse/HBASE-20656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503461#comment-16503461
 ] 

Hadoop QA commented on HBASE-20656:
-----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} docker {color} | {color:red}  1m 
22s{color} | {color:red} Docker failed to build yetus/hbase:d8b550f. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-20656 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12926747/HBASE-20656.master.006.patch
 |
| Console output | 
https://builds.apache.org/job/PreCommit-HBASE-Build/13110/console |
| Powered by | Apache Yetus 0.7.0   http://yetus.apache.org |


This message was automatically generated.



> 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, HBASE-20656.master.003.patch, 
> HBASE-20656.master.004.patch, HBASE-20656.master.005.patch, 
> HBASE-20656.master.006.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)

Reply via email to