hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Drob (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17730) Migration to 2.0 for coprocessors
Date Tue, 07 Nov 2017 22:28:00 GMT

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

Mike Drob commented on HBASE-17730:

Nope, the CP wasn't getting loaded at first.

> Migration to 2.0 for coprocessors 
> ----------------------------------
>                 Key: HBASE-17730
>                 URL: https://issues.apache.org/jira/browse/HBASE-17730
>             Project: HBase
>          Issue Type: Sub-task
>          Components: documentation, migration
>            Reporter: Appy
>            Priority: Blocker
>             Fix For: 2.0.0-beta-1
> Jiras breaking coprocessor compatibility should be marked with component ' Coprocessor',
and label 'incompatible'.
> Close to releasing 2.0, we should go through all such jiras and write down steps for
migrating coprocessor easily.
> The idea is, it might be very hard to fix coprocessor breakages by reverse engineering
errors,  but will be easier we suggest easiest way to fix breakages resulting from each individual
incompatible change.
> For eg. HBASE-17312 is incompatible change. It'll result in 100s of errors because BaseXXXObserver
classes are gone and will probably result in a lot of confusion, but if we explicitly mention
the fix which is just one line change - replace "Foo extends BaseXXXObserver" with "Foo implements
XXXObserver" - it makes it very easy.

This message was sent by Atlassian JIRA

View raw message