Administration of the MapR Database is done primarily via the command line (maprcli) or with the MapR Control System (MCS). Regardless of whether the MapR Database table is used for binary files or JSON documents, the same types of commands are used with slightly different parameter
options. MapR Database 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.

When auditing of table operations is enabled at the cluster level, volume level, and
filesystem level, each operation on a table is logged on the node where the operation
was executed, which could differ from the node where the operation was initiated.

Typical log entries provide a timestamp of the operation, the type of operation, the UID
of the user who ran the command, the IP address from which the user ran the command,
identifiers of the affected resources, and the status of the operation. Fields such as
“ColumnFamily” and “Column” for some operations are also included when applicable. Row
keys are not included. Status codes come from the Linux errno.h file.
For a list of these codes, see Status Codes That Can Appear in Audit Logs.

Note: Due to the way that the creation of tables is processed internally, sometimes the
creation of tables is logged in FSAudit.log.json, rather than in
DBAudit.log.json.

Note: Audit logs do not display the indices of array elements when there are put or update
operations on arrays that are in documents within JSON tables.

To convert the user IDs to usernames, file identifiers to pathnames, and volume IDs to
volume names, run the expandaudit utility. For example, here are the same audit records after they
were processed by this utility: