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
        Additional implemented C APIs
        C API for impersonation
        Specifying MapR-DB Binary Tables When Using the C APIs
        Installing the mapr-client Package
        Building and Launching Applications
        Sample Application for Accessing MapR-DB Tables
        Sample Application for Impersonation Support
        Thread-pool Settings for Improving Application Performance
        Support for HBase Java Filters by the MapR-DB C APIs
      - Creating Java Applications That Access MapR-DB Binary Tables
      - 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.

Specifying MapR-DB Binary Tables When Using the C APIs

In APIs in which you must pass the name of a MapR-DB table, you can specify the name in one of two ways:

Specify the complete path to the table in this format: /mapr/<cluster>/<volume>/<table> For example, if you were to use the nhb_admin_table_add_column_family API to add a new column family to a table, the name of the cluster was newyork, the name of the volume was vol1, and the name of the table was table1, you would specify the table with this path: /mapr/newyork/vol1/table1
Specify the name only. This method requires that you first modify the hbase.table.namespace.mappings property to the core-site.xml file. For Hadoop 1, edit the file /opt/mapr/hadoop/hadoop-0.20.2/conf/core-site.xml. For Hadoop 2, edit the file /opt/mapr/hadoop/hadoop-2.4.1/etc/hadoop/core-site.xml. Here is an example:

<property>
        <name>hbase.table.namespace.mappings</name>
        <value>*:/tables_dir1</value>
</property>

In this example, all tables that you create with the C APIs and all tables that you access will be in the directory /tables_dir1. If you specified the table name table1 in a C API, the full path to the table would be /tables_dir1/table1.