HPE Ezmeral Data Fabric 6.1.x is In Maintenance and transitions to "End of Maintenance" in June 2024. Please see the latest documentation.

About MapR 6.1
This site contains the main documentation for Version 6.1 of the MapR Converged Data Platform, including installation, configuration, administration, and reference information.
6.1 Installation
This section contains information about installing and upgrading MapR software. It also contains information about how to migrate data and applications from an Apache Hadoop cluster to a MapR cluster.
6.1 MapR Data Platform
MapR Data Platform is the industry-leading data platform for AI and analytics that solves enterprise business needs.
6.1 Administration
This section describes how to manage the nodes and services that make up a cluster.
6.1 Development
This section contains information related to application development for Ezmeral ecosystem components and MapR Data Platform products, including the file system, Database (Key-Value and JSON), and Event Streams.
- Application Development Process
  Before you start developing applications on the MapR Data Platform platform, consider how you will get the data into the platform, the storage format of the data, the type of processing or modeling that is required, and how the data will be accessed.
- MapR XD and Apps
  The following sections provide information about accessing the MapR XD with C and Java applications.
- MapR Database and Apps
  This section contains information about developing client applications for JSON and key-value tables.
- MapR Event Store For Apache Kafka and Apps
  MapR Event Store For Apache Kafka brings integrated publish and subscribe messaging to MapR Data Platform.
- MapReduce and Apps
  This section contains information associated with developing YARN applications.
- MapR Data Science Refinery
  The MapR Data Science Refinery product is an easy-to-deploy and scalable data science toolkit with native access to all platform assets and superior out-of-the-box security.
- MapR Data Fabric for Kubernetes
  This section describes how to leverage the capabilities of the MapR Data Fabric for Kubernetes.
  - MapR Container Storage Interface (CSI) Storage Plugin
    This section describes how to use and troubleshoot the MapR Container Storage Interface (CSI) Storage Plugin.
  - Kubernetes FlexVolume Driver
    This section describes how to use and troubleshoot the MapR Data Platform for Kubernetes FlexVolume Driver.
    - Using
      This section describes how to configure Kubernetes objects to enable persistent storage and includes example configuration files for static and dynamic provisioning.
    - Troubleshooting
      This section describes how to resolve common problems you might encounter when using the MapR Data Fabric for Kubernetes FlexVolume driver.
- Ecosystem Components
  The following sections provide information about each open-source project that is supported by the MapR Data Platform.
- 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
  MapR Data Platform supports public APIs for MapR File System, MapR Database, and MapR Event Store For Apache Kafka. These APIs are available for application-development purposes.
Other Docs
This section contains release-independent information, including: MapR Installer documentation, Ecosystem release notes, interoperability matrices, security vulnerabilities, and links to other MapR version documentation.
Glossary
Definitions for commonly used terms in MapR Converged Data Platform environments.

Enabling the Platinum Posix Client for MapR Data Fabric for Kubernetes FlexVolume Driver

When you install the MapR Data Fabric for Kubernetes FlexVolume Driver, the Basic FUSE-based POSIX client package is installed on all nodes by default. The FlexVolume Driver also supports the use of the Platinum FUSE-based POSIX client. For a comparison of the two POSIX client packages, see Preparing for Installation (MapR POSIX Client).

To install the Platinum POSIX client, include the platinum parameter in your Pod spec. For example:

options:
cluster: "cluster2"
platinum: "true"
cldbHosts: "10.10.102.96"