Administration of the MapR-DB is done primarily via the command line (maprcli) or with the MapR Control System (MCS). Regardless of whether the MapR-DB table is used for binary files or JSON documents, the same types of commands are used with slightly different parameter options. MapR-DB administration is associated with tables, columns and column families, and table regions.

The MapR Data Access Gateway is a service that acts as a proxy and gateway for translating requests between lightweight client applications and the MapR cluster. This section describes considerations when upgrading the service, how to modify configuration settings, and how to administer and manage the service.

These maprcli commands are used to create and manage Change Data Capture (CDC) changelogs. A changelog is used to establish a relationship between a MapR-DB source table (JSON or binary) and a MapR-ES stream topic and to manage the propagation process.

Note: The mapr user is not treated as a superuser.
MapR-DB does not allow the mapr user to run this command unless that user
is given the relevant permission or permissions with access-control expressions.

Parameters

Parameter

Description

path

The path to the replica.

For a path to a table on the local cluster, start the path at the volume mount
point. For example, for a table named testdst under volume1
which has a mount point at /volume1, specify the following path:
/volume1/testdst

For a path to a table on a remote cluster, you must also specify the cluster
name in the path. For example, for a table named customerdst
under volume1 in the sanfrancisco cluster, specify the following path:
/mapr/sanfrancisco/volume1/customerdst

upstream

The path to the source table.

For a path on the local cluster, start the path at the volume mount point. For
example, for a table named testsrc under volume1 which has a
mount point at /volume1, specify the following path:
/volume1/testsrc

For a path on another cluster, you must also specify the cluster name in the
path. For example, for a table named customersrc under volume1
in the sanfrancisco cluster, specify the following path:
/mapr/sanfrancisco/volume1/customersrc