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.
- Ecosystem Components
  The following sections provide information about each open-source project that is supported by the MapR Data Platform.
  - Ezmeral Ecosystem Packs
  - AsyncHBase
    - Configuring the Default Database for AsyncHBase
      For AsynchHBase 1.7 and later, you can configure whether AsyncHBase accesses HBase tables or MapR-DB tables by default. If this value is not configured, AsyncHBase will determine the table type.
    - Compiling and Running AsyncHBase Applications
      When you compile or run AsyncHBase applications, you need to include the required AsyncHBase libraries.
    - AsyncHBase Script
      MapR provides an AsyncHBase script that you can use to run applications and generate the AsyncHBase classpath.
    - AsyncHBase Behavior with MapR Database Binary Tables
      After you install AsyncHBase, you can use the AsyncHBase libraries to provide asynchronous access to MapR Database binary tables. However, it is important to note the behavior that is specific to using AsyncHBase with MapR Database.
    - Using OpenTSDB with AsyncHBase
      OpenTSDB can use MapR’s AsyncHBase to perform time-series data-plots on MapR Database binary tables.
    - GetRequest API
      MapR includes an additional constructor for the GetRequest class which takes an extra qualifier.
  - Cascading
  - Apache Drill
  - Flume
  - HBase
  - HBase Client and MapR Database Binary Tables
  - HCatalog
  - Hive
  - HttpFS
  - Hue
  - Impala
  - Livy
    Apache Livy is primarily used to provide integration between Hue and Spark.
  - MapR Event Store For Apache Kafka Clients and Tools
    Describes the supported MapR Event Store For Apache Kafka tools and clients.
  - S3 Gateway
    The S3 gateway is a service that provides an S3-compatible interface to expose data in MapR Data Platform as objects. The S3 gateway manages all inbound S3 API requests to put data into and get data out of cloud storage.
  - Myriad
  - Oozie
  - Pig
  - Sentry
  - Apache Spark
  - Sqoop
  - YARN
  - Zeppelin
- 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.

AsyncHBase Behavior with MapR Database Binary Tables

After you install AsyncHBase, you can use the AsyncHBase libraries to provide asynchronous access to MapR Database binary tables. However, it is important to note the behavior that is specific to using AsyncHBase with MapR Database.

The Scanner.setMaxNumKeyValues method, when run against MapR Database binary tables, does not behave as documented.: According to the AsyncHBase documentation, this method sets “the maximum number of KeyValues the server is allowed to return in a single RPC response.”
When you use this method with MapR Database binary tables, the value for the maximum number of key values is ignored and the full set of KeyValues is always returned.

List<RegionClientStats> regionStats() is not supported: As of AsyncHBase 1.7-1603, List<RegionClientStats> regionStats() is not supported and when it is used the API does not return statistics.

MapR Database ignores HBase configurations in the asynchbase.conf file: As of AsyncHBase 1.7-1603, the conf object can be used to override Hbase properties that were previously only configured in the asynchbase.conf file. The asynchbase.conf file is located in the asynchbase installation directory. MapR Database does not use these Hbase configurations and therefore they are ignored by MapR Database