Home
6.0 Platform
Provides a brief overview of what the MapR data platform is and how you can use it to solve enterprise business needs.
MapR-DB
MapR-DB is an enterprise-grade, high-performance, NoSQL database management system. You can use it for real-time, operational analytics capabilities.
Table Replication
Data in one table can be replicated to another table that is in the same cluster or in a separate cluster. This type of replication is in addition to the automatic replication that occurs with table regions within a volume.

MapR 6.0 Documentation

6.0 Platform
Provides a brief overview of what the MapR data platform is and how you can use it to solve enterprise business needs.
- MapR-XD
- MapR-DB
  MapR-DB is an enterprise-grade, high-performance, NoSQL database management system. You can use it for real-time, operational analytics capabilities.
  - Architecture
    MapR-DB is an enterprise-grade, high performance, NoSQL (“Not Only SQL”) database management system. You can use it to add realtime, operational analytics capabilities to big data applications. As a multi-model NoSQL database, it supports both JSON document models and wide column data models.
  - Data Models
    MapR-DB can be used as both a document database and a wide-column database. As a document database, JSON documents are stored in MapR-DB JSON table. As a wide-column database, binary files are in stored MapR-DB binary tables.
  - Secondary Indexes
    Beginning with MapR 6.0, MapR-DB JSON natively supports secondary indexes on fields in JSON tables. Indexes provide you with flexible, high performance access to data stored in MapR-DB.
  - Change Data Capture
    The Change Data Capture (CDC) system allows you to capture changes made to data records in MapR-DB tables (JSON or binary) and propagate them to a MapR-ES topic.
  - Table Replication
    Data in one table can be replicated to another table that is in the same cluster or in a separate cluster. This type of replication is in addition to the automatic replication that occurs with table regions within a volume.
    - Modes of replication
    - Supported replication topologies
    - Gateways for Replicating MapR-DB Tables
      In MapR-DB table replication, MapR-DB replicates updates to tables (binary and JSON) on source MapR clusters to replicas of those tables on destination MapR clusters. Gateways are services that receive these updates and apply them to the replicas. These gateways also propagate updates from JSON tables to their secondary indexes.
    - Replica Autosetup for MapR-DB Tables
      The option to automatically set up table replication, also known as replica autosetup, performs the steps to set up and start the replication of MapR-DB binary table and MapR-DB JSON tables. The replica autosetup option is available through the MCS and maprcli.
    - Table Replication States
      The replication state indicates when table replication is in progress and it also displays the status of operations related to replica autosetup. The maprcli table replica list command displays the following replication states.
    - Order of writes at replicas
    - Security and Replication
    - Licensing
  - Gateways for Indexing MapR-DB Data in Elasticsearch
    As of with MapR 6.0, MapR-DB Elastic Search integration capability is deprecated and no longer available in the MapR-DB product.
- MapR-ES
  MapR-ES brings integrated publish and subscribe messaging to the MapR Converged Data Platform.
- Cluster Management
- Security
- YARN
- Client Connections

Table Replication

Data in one table can be replicated to another table that is in the same cluster or in a separate cluster. This type of replication is in addition to the automatic replication that occurs with table regions within a volume.

You can replicate changes (puts and deletes), entire tables, specific column families, and specific columns.

NOTE: MapR binary tables can only be replicated to binary tables; MapR JSON tables can only be replicated to JSON tables.

Tables that data is replicated from are called source tables, while tables that data is replicated to are called replicas.
Clusters that data is replicated from are called source clusters. Clusters that data is replicated to are called destination clusters. A single cluster can be both a source cluster and a destination cluster, depending on the replication configuration in which the cluster participates.
Replication takes place between source and destination clusters. However, source clusters do not send data to nodes in the destination cluster directly. The replication stream (the data being pushed to the replicas) is consumed by one or more MapR gateways in the destination cluster. The gateways receive the updates from the source cluster, batch them, and apply them to the replica tables. Multiple gateways serve the purpose of both load balancing and failover.

For more information about gateways, see “Administering MapR Gateways.

NOTE: The maximum number of replicas that a source table can replicate to is 64. The maximum number of source tables that a replica can accept updates from is 64.