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
  - Cascading
  - Apache Drill
  - Flume
  - HBase
  - HBase Client and MapR Database Binary Tables
  - HCatalog
  - Hive
  - HttpFS
  - Hue
  - Impala
    - New Features in Impala
    - Additional Impala Configuration Options
    - Working with Impala
    - Impala Security
      - Enable Kerberos Authentication
      - Enable SSL for Impala
      - LDAP Authentication
      - Sentry
        Sentry Feature Support
        The global-policy.ini File
        Configuring Sentry
        The steps to configure Sentry are determined by the storage model, the type of security used by the cluster, and the components that will use Sentry authorization.
        Integrating Sentry
        Integrate Sentry with other ecosystem components to enable those components to use Sentry authorization. You can also integrate Sentry with Hue in order to use the Hue Security application to manage Sentry privileges and roles.
        Configure Impala to Use Sentry Authorization
        You can configure Impala to work with Sentry for authorization. When you configure Sentry authorization for Impala, Impala uses operating system IDs to associate privileges with each user that runs the impala-shell or client program.
        Configure Impala to Use Sentry Authorization With the Database Storage Model
        As of Sentry 1.6, Sentry can be configured to use the Database storage model. Complete the following steps to configure Impala to use Sentry authentication when Sentry uses the DB storage model:
        Configure Impala to Use Sentry Authorization in File-Based Storage Model
        Impala reads the file and controls which objects users can access and what operations they can perform on the objects. Impala caches the security information in the policy file every five minutes. If you make significant changes to security policies, restart Impala. Changes immediately take effect.
        Configure Sqoop2 to use Sentry Authorization
        As of Sentry 1.6.0, you can configure Sqoop2 to use Sentry authentication when Sentry uses the database storage model, the cluster is secure, and the cluster uses Kerberos authentication. Use these steps:
        Configure Hive to use Sentry Authorization
        Configure Hive to use Sentry when you want to use Sentry authorization with Impala.
        Integrate Hue with Sentry
        You can integrate Hue with Sentry 1.6 on a secure cluster that uses Kerberos authentication; however, the integration is not supported on a secure cluster using MapR-SASL authentication. Integrate Hue with Sentry when you want to use the Hue Security application to manage Sentry roles and privileges. When you integrate Hue with Sentry, Sentry must use the database storage model.
        Sentry 1.7.0 API Changes
  - 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.

Configure Impala to Use Sentry Authorization With the Database Storage Model

As of Sentry 1.6, Sentry can be configured to use the Database storage model. Complete the following steps to configure Impala to use Sentry authentication when Sentry uses the DB storage model:

About this task

IMPORTANT This component is deprecated. Hewlett Packard Enterprise recommends using an alternate product. For more information, see Discontinued Ecosystem Components.

Procedure

Set the following properties in env.sh (/opt/mapr/impala/impala-<version>/conf/env.sh):
```
IMPALA_SERVER_ARGS=" -server_name=HS2 -sentry_config=<SENTRY-HOME>/conf/sentry-site.xml
IMPALA_CATALOG_ARGS=" -sentry_config=<SENTRY-HOME>/conf/sentry-site.xml
IMPALA_STATE_STORE_ARGS=" -sentry_config=<SENTRY-HOME>/conf/sentry-site.xml
```
NOTE SENTRY-HOME is a variable used in place of the ecosystem component home directory. Typically, the default ecosystem component home directory for a component is /opt/mapr/<component>/<component>-<version>/.

Run the following commands to restart Impala:

sudo -u mapr maprcli node services -name impalaserver -action restart -nodes <nodename>

sudo -u mapr maprcli node services -name impalastore -action restart -nodes <nodename>

sudo -u mapr maprcli node services -name impalacatalog -action restart -nodes <nodename>

When Impala is running, you can issue the following command to start the impala-shell as a particular user:
```
impala-shell -u <user_name>
```