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.
Oozie
Configure Oozie
Updating the Oozie Shared Libraries

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.

Updating the Oozie Shared Libraries

About this task

By default, the Oozie shared libraries are uploaded to the maprfs:///oozie/share/lib directory. If you have not changed the oozie.service.WorkflowAppService.system.libpath property in the oozie-site.xml file, Oozie will update and upload the shared libraries automatically after rebuilding the Oozie war file. Or you can update sharelib without rebuilding the war file by using the following steps.

If the oozie.service.WorkflowAppService.system.libpath property in the oozie-site.xml file was changed from the default value (/oozie/share/lib), you must perform the following steps to update the shared libraries:

Procedure

Based on the cluster MapReduce mode, run one of the following commands to copy the new Oozie shared libraries to MapR-FS:

Cluster MapReduce Mode	Command
YARN	`{OOZIE_HOME}/bin/oozie-setup.sh sharelib create -fs maprfs:/// -locallib /opt/mapr/oozie/oozie-<version>/share2`
Classic	`{OOZIE_HOME}/bin/oozie-setup.sh sharelib create -fs maprfs:/// -locallib /opt/mapr/oozie/oozie-<version>/share1`

Run the following command to update the Oozie classpath with the new shared libraries:
```
{OOZIE_HOME}/bin/oozie admin -sharelibupdate
```