Before you start developing applications on MapR’s Converged Data Platform, consider how you will get the data onto the
platform, the format it will be stored in, the type of processing or modeling that is required, and how the data will
be accessed.

A MapR Ecosystem Pack (MEP) provides a set of ecosystem components that work together on one or more MapR cluster versions. Only one version of
each ecosystem component is available in each MEP. For example, only one version of Hive and one version of Spark is supported in a MEP.

The metadata for Hive tables and partitions are stored in the Hive Metastore. By default, the Hive Metastore stores
all Hive metadata in an embedded Apache Derby database in the MapR file system. Derby only allows one connection at
a time; if you want multiple concurrent Hive sessions, you can use MySQL for the Hive Metastore.

Note: Though you can set the same hive-site.xml properties on
all the hosts (client, Metastore, HiveServer),
hive.metastore.uris is the only property that must be
configured on all the hosts; the other properties are only needed on the
Metastore host.