MapR 5.1 is at End of Life (EOL) and no longer supported. Please see the latest documentation. This documentation is not being updated.

5.1 DB & Streams
This section covers the MapR-DB, MapR-Streams, and MapR-Gateways features. Each feature may contain both administrator and developer topics.
- MapR-DB
  - Architecture of MapR-DB
    MapR-DB's architecture gives it a large of advantages over other NoSQL databases.
  - Performance Enhancements for SSD Based MapR-DB Deployments
  - MapR-DB as a Document Database
    MapR-DB supports OJAI documents as a native data store. OJAI documents are stored in a compact binary format, not as plain ASCII text.
  - MapR-DB as a Wide-Column Database
    - Logical Model of MapR-DB Binary Tables
    - Filesystem Operations on MapR-DB Tables
    - Migrating Between Apache HBase Tables and MapR-DB Binary Tables
    - Designing Row Keys for MapR-DB Binary Tables
      A row key identifies a row in a MapR-DB binary table.
    - Designing Column Families for MapR-DB Binary Tables
      Scanning an entire table for matches can be very performance-intensive. Column families enable you to group related sets of data and restrict queries to a defined subset, leading to better performance. When you design a column family, think about what kinds of queries are going to be used the most often, and group your columns accordingly.
    - Configuring Maximum Row Sizes for Binary Tables
      The default maximum row size at installation is 32MB. You can configure this maximum by changing the value of the mfs.db.max.rowsize.kb parameter with the maprcli config save command.
    - Enabling Access to MapR Tables via HBase APIs, hbase shell, and MapReduce Jobs
    - Creating MapR-DB Binary Tables
    - Displaying Table Region Information for MapR-DB Tables
    - Creating Applications That Access MapR-DB Binary Tables
      - Mapping Table Namespace Between Apache HBase Tables and MapR-DB Binary Tables
      - Behavior of the MapR dbclient When Connecting to MapR-DB
        Requests from client applications to connect to MapR-DB are handled by the MapR dbclient. This dbclient has the following behaviors when establishing the first connection and when re-establishing connections after the CLDB goes offline.
      - Creating C Applications That Access MapR-DB Binary Tables
      - Creating Java Applications That Access MapR-DB Binary Tables
        Using Maven to Manage Dependencies
        Supported and Unsupported Methods in Admin (HBase 0.98 and higher)
        This table indicates which methods MapR-DB supports in the HBase interface Admin.
        Supported and Unsupported Methods in BufferedMutator (HBase 0.98 and higher)
        This table indicates which methods MapR-DB supports in the HBase interface BufferedMutator.
        Supported and Unsupported Methods in Connection (HBase 0.98 and higher)
        This table indicates which methods MapR-DB supports in the HBase interface Connection.
        Supported and Unsupported Methods in ConnectionFactory (HBase 0.98 and higher)
        This table indicates which methods MapR-DB supports in the HBase class ConnectionFactory.
        Supported and Unsupported Methods in RegionLocator (HBase 0.98 and higher)
        This table indicates which methods MapR-DB supports in the HBase interface RegionLocator.
        Supported and Unsupported Methods in Table (HBase 0.98 and higher)
        This table indicates which methods MapR-DB supports in the HBase interface Table.
        Support for HBase Java Filters
        Support for HBase Java comparators
        Unsupported Methods in the Append, Delete, Increment, Put, and Scan Classes
      - Tuning Parameters for Client Applications That Access MapR-DB Binary Tables
        Though tuning client applications is generally not necessary, MapR does offer tuning parameters to change the behavior of client-side caching.
      - Building and Running MapReduce Applications That Access MapR-DB Binary Tables
    - Bulk Loading and MapR-DB Binary Tables
    - Replicating MapR-DB Binary Tables
    - Indexing MapR-DB Binary Tables with Elasticsearch
    - Impersonation via the HBase REST Gateway
- MapR Streams
  MapR Streams brings integrated publish/subscribe messaging to the MapR Converged Data Platform.
- MapR Gateways
  A MapR gateway mediates one-way communication between a source MapR cluster and a destination cluster. MapR-DB binary tables and MapR Streams streams can be replicated.

Using Maven to Manage Dependencies

If you want to use MapR-DB with your Maven application, follow these instructions to set up the POM file to manage your Maven dependencies.

Edit the `pom.xml` File

Add MapR's maven repository to the list of repositories in your application's pom.xml. For example:

<repository>
      <id>mapr-releases</id>
      <url>http://repository.mapr.com/maven/</url>
      <snapshots><enabled>true</enabled></snapshots>
      <releases><enabled>true</enabled></releases>
</repository>

For client applications, edit the pom.xml file and add the following entry in the dependencies tag.

<groupId>org.apache.hbase</groupId>
<artifactId>hbase-client</artifactId>

For server and map-reduce applications, add the following entry in the dependencies tag in the pom.xml file.

<groupId>org.apache.hbase</groupId>
<artifactId>hbase-server</artifactId>

Add the Version Tags

MapR-DB supports both HBase 0.98 and HBase 1.1 APIs. For the version tags, specify the version used by your application. The JAR file versions are listed in the following locations.

Client applications	http://repository.mapr.com/nexus/content/groups/mapr-public/org/apache/hbase/hbase-client/
Server applications	http://repository.mapr.com/nexus/content/groups/mapr-public/org/apache/hbase/hbase-server/

Copy and paste the version you need into the <version> tags in the POM file for your HBase client application or HBase server application.

NOTE: When defining the version for your application, specifying the version without m7-<maprversion> will limit access to HBase tables only. Ensure that the version tags include reference to m7-<maprversion> if you want your applications to access MapR-DB also.

For example, if you are using HBase 0.98.12, you can add the following in the dependencies tag.

<groupId>org.apache.hbase</groupId>
<artifactId>hbase-client</artifactId>
<version>0.98.12-mapr-1506-m7-5.1.0</version>

If you are using HBase 1.1, you can add the following in the dependencies tag.

<groupId>org.apache.hbase</groupId>
<artifactId>hbase-client</artifactId>
<version>1.1.1-mapr-1602-m7-5.1.0</version>