MapR 5.2 is at End of Life (EOL) and no longer supported. Please see the latest documentation. This documentation is not being updated.

Home
5.2 Application Development
This section contains information related to application development for ecosystem components and MapR products including MapR-DB (binary and JSON), MapR-FS, and MapR Streams.
Ecosystem Components
The following sections provide information about each open source project that MapR supports.
MapR Expansion Packs
A MapR Expansion 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.

MapR 5.2 Documentation

5.2 Application Development
This section contains information related to application development for ecosystem components and MapR products including MapR-DB (binary and JSON), MapR-FS, and MapR Streams.
- Connecting to the Cluster
  Application are often run on nodes that are not part of the MapR Cluster. There are many methods to connect to a MapR cluster; this section will briefly describe each option.
- MapR-FS and Applications
  The following sections provide information about accessing MapR-FS with C and Java applications.
- MapR-DB and Applications
  This section contains information on developing client applications for binary and JSON tables.
- MapR Streams and Applications
  MapR Streams brings integrated publish/subscribe messaging to the MapR Converged Data Platform.
- MapReduce and Applications
  This section contains information associated with developing MapReduce programs or YARN applications.
- Ecosystem Components
  The following sections provide information about each open source project that MapR supports.
  - MapR Expansion Packs
    A MapR Expansion 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.
  - AsyncHBase
  - Cascading
  - Drill
  - Flume
  - HBase
  - HCatalog
  - Hive
  - HttpFS
  - Hue
  - Impala
  - Mahout
  - MapR Streams Clients and Tools
  - Myriad
  - Oozie
  - Pig
  - OpenStack Sahara (Ocata)
  - Sentry
  - Spark
  - Sqoop
  - Storm
  - Third Party Solutions
- Maven and MapR
  This section discusses topics associated with Maven and MapR.
- Developer's Reference
  This section contains in-depth information for the developer.
- API Documentation
  This topic provides links to the locations of MapR's public APIs. These APIs are available for application development purposes.

MapR Expansion Packs

A MapR Expansion 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.

MapR creates a new MEP version when a new ecosystem component is available or a patch is applied to an ecosystem component that is already in a released MEP.

A single version of MapR core may support multiple MEPs, but only one at a time. For a list of currently supported MEPs and detailed information about each MEP, see MapR Expansion Packs (MEPs).

The following open source components are included in the MEP for internal MapR Monitoring use cases only:

Collectd
Elasticsearch
Fluentd
Grafana
Kibana
OpenTSDB

NOTE: Developer previews for fast-moving ecosystem components will continue to be available in addition to MEPs. However, developer preview releases of ecosystem components are not tested for production environments, and they do not undergo the same interoperability testing.

For more information, see the MapR Expansion Pack Release Notes.