Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-13428 [DOC] Migration to hbase-2.0.0
  3. HBASE-17730

[DOC] Migration to 2.0 for coprocessors

    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0.0
    • Component/s: documentation, migration
    • Labels:
      None

      Description

      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.

        Attachments

        1. HBASE-17730.master.001.patch
          4 kB
          Apekshit Sharma

          Activity

            People

            • Assignee:
              appy Apekshit Sharma
              Reporter:
              appy Apekshit Sharma
            • Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: