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.

Starting with MapR Ecosystem Pack (MEP) 6.0.0, MapR Object Store with S3-Compatible API (MapR Object Store) is included in MEP repositories. To fully benefit from the MapR Object Store, it is important to understand what the MapR Object Store
is and how it works, how to authenticate it and perform bucket operations.

MapR supports public APIs for MapR Filesystem, MapR Database, and MapR Event Store For Apache Kafka. These APIs are available for application development purposes.

Sqoop2

Note: Sqoop2 is only supported for use with Hue and has been deprecated as of Hue 4.3.

Sqoop2
transfers bulk data between Hadoop and various types of structured
datastores, such as relational databases, enterprise data
warehouses, and NoSQL systems. Sqoop2 is installed and configured
server-side. When you install the Sqoop2 server package, the
Sqoop2 client package is installed as well.

Sqoop2
can be used in conjunction with Hue, which is a web-based GUI that
facilitates the importing and exporting of data from these
structured datastores. This illustration shows how a
user can access Sqoop2 from a browser, such as Hue.

This documentation provides all relevant details about using Sqoop2 with MapR, but does not
duplicate Apache documentation. You can refer also to documentation available from the
Apache Sqoop
website.