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

About Release 6.2
This site contains documentation for HPE Ezmeral Data Fabric release 6.2 including installation, configuration, administration, and reference content, as well as content for the associated bundled ecosystem components and drivers.
6.2 Installation
This section contains information about installing and upgrading HPE Ezmeral Data Fabric software. It also contains information about how to migrate data and applications from an Apache Hadoop cluster to a HPE Ezmeral Data Fabric cluster.
- Planning the Cluster
  Describes information and factors used in planning your cluster.
- Installing Core and Ecosystem Components
  Describes how to install HPE Ezmeral Data Fabric software and ecosystem components with or without the Installer.
- Installing the File Migration Service on the Edge Cluster
  Describes how to install the File Migration service on CentOS nodes.
- Installing the HPE Ezmeral Data Fabric File Store
  Describes how to install File Store software with or without the Installer.
- Installing Kubernetes Interfaces for Data Fabric
  This section describes how to plan for and install the Container Storage Interface (CSI) Storage Plugin and the Kubernetes Interfaces for Data Fabric FlexVolume Driver.
- Upgrading Core or EEP Components
  Depending on your current configuration, you may choose to upgrade the release version (core), ecosystem components, clients, or monitoring components.
  - Upgrade Workflows (Release 6.1.x to 6.2)
    This section describes three common methods for upgrading from one core release to another. The workflows in this section introduce you to the high-level steps for each method and provide links to pages showing more detail.
  - Upgrading Core
    Describes the process of upgrading core.
  - Upgrading Ezmeral Ecosystem Packs
    Describes how to upgrade Ezmeral Ecosystem Packs (EEPs), either as part of a core upgrade or to take advantage of a new EEP for the current version of core.
    - Planning Ezmeral Ecosystem Pack (EEP) Upgrades
      The set of ecosystem components that you run in the cluster must all belong to the same EEP.
    - Preparing to Upgrade the Ezmeral Ecosystem Pack
      Complete these pre-upgrade steps for each ecosystem component in the EEP that you want to upgrade.
    - Upgrading the Ezmeral Ecosystem Pack With the Installer
      If the cluster that you want to upgrade was installed using the Installer, you can use the Installer to upgrade the Ezmeral Ecosystem Pack (EEP).
    - Upgrading the Ezmeral Ecosystem Pack Without the Installer
      After you upgrade core without using the Installer, you need to upgrade ecosystem components with manual steps. First, verify that your repository is configured to use an Ezmeral Ecosystem Pack (EEP) that is supported by your cluster version. Then, upgrade each component manually.
      - Upgrading AsyncHBase Libraries
        This section describes how to upgrade the AsyncHBase Libraries without the Installer.
      - Upgrading Drill
        This section describes how to upgrade Drill without the Installer.
      - Upgrading Flume
        This section describes how to upgrade Flume without the Installer.
      - Upgrading Hadoop and YARN
        This section describes how to upgrade Hadoop and YARN without the Installer.
      - Upgrading HBase
        This section describes how to upgrade HBase without the Installer.
      - Upgrading HBase Client and Tools
        This section describes how to upgrade HBase Client and other tools without the Installer.
      - Upgrading Hive
        This section describes how to upgrade Hive without the Installer.
      - Upgrading HttpFS
        This section describes how to upgrade HttpFS without the Installer.
      - Upgrading Hue
        This section describes how to upgrade Hue without the Installer.
      - Upgrading Impala
        This section describes how to upgrade Impala without the Installer.
      - Upgrading the Data Access Gateway
        This section describes how to upgrade the Data Access Gateway without the Installer.
      - Upgrading Livy
      - Upgrading Monitoring
        Complete the following steps to upgrade Monitoring without the Installer.
      - Upgrading the S3 Gateway
        This topic provides instructions for manually updating the Object Store version 2.0.x to 2.1.x on an edge node or server node that is running core software. When you upgrade, Object Store configurations are automatically migrated. If LDAP integration is enabled, verify that the policies and configurations are correct after migration.
      - Upgrading the HPE Ezmeral Data Fabric Streams Python Client
        This section describes how to upgrade the HPE Ezmeral Data Fabric Streams Python Client without the Installer.
      - Upgrading HPE Ezmeral Data Fabric Streams Tools
        Complete the following steps to upgrade HPE Ezmeral Data Fabric Streams Tools without the Installer.
      - Upgrading Oozie
        This section describes how to upgrade Oozie without the Installer.
      - Upgrading Pig
        This section describes how to upgrade Pig without the Installer.
      - Upgrading Sentry
        This section describes how to upgrade Sentry without the Installer.
      - Upgrading Spark Standalone
        This section describes how to upgrade Spark Standalone without the Installer.
      - Upgrading Spark on YARN
        This section describes how to upgrade Spark on YARN without the Installer.
      - Upgrading Sqoop1
        This section describes how to upgrade Sqoop1 without the Installer.
      - Upgrading Tez
        This section describes how to upgrade Tez without the Installer.
    - Finishing the Ezmeral Ecosystem Pack Upgrade
      Complete the post-upgrade steps for each ecosystem component that was upgraded.
  - Preparing the Cluster for a Maintenance Update
    This section identifies how to prepare for applying either a minor update or a patch.
  - Performing a Maintenance Update
    Perform a maintenance update when you want to upgrade to a new patch version of core or apply a patch.
- Setting Up Clients and Services
  Describes how to set up and use interfaces to an HPE Ezmeral Data Fabric cluster from a client computer.
- Setting Up the Control System
  Describes how to configure and access the Control System.
- Migrating to the HPE Ezmeral Data Fabric
  Provides instructions for migrating business-critical data and applications from an Apache Hadoop cluster to an HPE Ezmeral Data Fabric cluster.
- Applying a Patch
  You can apply a patch by using the Installer, by using the command line (a manual process), or by using an Installer Stanza.
6.2 Data Fabric
HPE Ezmeral Data Fabric is the industry-leading data platform for AI and analytics that solves enterprise business needs.
6.2 Administration
This section describes how to manage the nodes and services that make up a cluster.
6.2 Development
This section contains information related to application development for Ezmeral ecosystem components and HPE Ezmeral Data Fabric products, including the file system, Database (Key-Value and JSON), and Event Streams.
Other Docs
This section contains release-independent information, including: Installer documentation, Ecosystem release notes, interoperability matrices, security vulnerabilities, and links to other data-fabric version documentation.
Glossary
Definitions for commonly used terms in MapR Converged Data Platform environments.

Upgrading Pig

This section describes how to upgrade Pig without the Installer.

About this task

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

Complete the following steps to upgrade Pig without the Installer.

Procedure

Run the following command to upgrade Pig using a package manager:

On RedHat and CentOS

yum update mapr-pig

On Ubuntu

apt-get install mapr-pig

On SLES

zypper update mapr-pig

What to do next

To apply custom configurations to the new version, migrate any custom configuration settings into the new default files in the conf directory. See Post-Upgrade Steps for Pig.