Before You Start

Before migrating your tables to another platform, consider the following points:

  • Schema Changes. Apache HBase and MapR-DB tables have different limits on the number of column families. If you are migrating to MapR, you may be interested in changing your table's schema to take advantage of the increased availability of column families. Conversely, if you're migrating from MapR-DB tables to Apache, you may need to adjust your schema to reflect the reduced availability of column families.
  • API Mappings: If you are migrating from Apache HBase to MapR-DB tables, examine your current HBase applications to verify the APIs and HBase shell commands used are fully supported.
  • Namespace Mapping: If the migration will take place over a period of time, be sure to plan your table namespace mappings in advance to ease the transition.
  • Implementation Limitations: MapR-DB tables do not support HBase coprocessors. If your existing Apache HBase installation uses coprocessors, plan any necessary modifications in advance. MapR-DB tables support a subset of the regular expressions supported in Apache HBase. Check your existing workflow and HBase applications to verify you are not using unsupported regular expressions.

If you are migrating to MapR-DB tables, be sure to change your Apache HBase client to the MapR client by installing the version of the mapr-hbase package that matches the version of Apache HBase on your source cluster.

See Installing MapR Software for information about MapR installation procedures, including setting up the proper repositories.