[jira] [Comment Edited] (HBASE-17730) [DOC] Migration to 2.0 for coprocessors

["Appy (JIRA)" <ji...@apache.org>]

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

Appy edited comment on HBASE-17730 at 4/4/18 8:04 PM:
------------------------------------------------------

Oh! Thanks [~psomogyi] for pointing it out. Correcting it.

And committing the docs change....


was (Author: appy):
Oh! Thanks [~psomogyi] for pointing it out. Correcting it.

 

> [DOC] 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
>            Assignee: Appy
>            Priority: Blocker
>             Fix For: 2.0.0
>
>         Attachments: HBASE-17730.master.001.patch
>
>
> 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
(v7.6.3#76005)