Discontinued Ecosystem Components

This page provides information about discontinued ecosystem components.

Ecosystem components can be discontinued when either of the following is true:
  • Newer components are available that serve the same function but provide better features and performance.
  • The Open Source community decides to retire a product.

To understand what discontinued and deprecated mean when these terms are applied to a component or MEP, see Understanding the MEP Lifecycle.

HPE uses the support advisory process to notify users well in advance that a component will be discontinued. The last MEP version to support a deprecated component is the MEP version that is released at the time of the deprecation announcement. The following table lists the components that are either already discontinued or scheduled to be discontinued:
Component Deprecated Discontinued Last MEP Version Supporting Component* Suggested Replacement Announcement
Impala June 1, 2021 December 31, 2021
  • MEP 7.1.0
  • MEP 6.3.4
  • MEP 5.0.7
Spark or equivalent partner product. See the HPE Technology Partner website. June 2021
Sentry June 1, 2021 December 31, 2021
  • MEP 7.1.0
  • MEP 6.3.4
  • MEP 5.0.7
None June 2021
Myriad September 2020 See note**
  • MEP 5.0.x
  • MEP 6.3.x
Kubernetes MapR Marketing Newsletter
Sqoop2 September 2020 See note**
  • MEP 5.0.x
  • MEP 6.3.x
Equivalent partner product. See the HPE Technology Partner website. MapR Marketing Newsletter
Mahout October 2017 April 2019
  • MEP 3.0.5
None MapR Marketing Newsletter
Mezos October 2017 April 2019
  • MEP 3.0.2
Kubernetes MapR Marketing Newsletter
Storm October 2017 April 2019
  • MEP 3.0.5
None MapR Marketing Newsletter
Hue-Livy October 2017 April 2019
  • MEP 3.0.5
Livy MapR Marketing Newsletter

*Later MEPs in the same series can include a discontinued component. For example, if the last MEP version supporting a discontinued component is x.y.0, the component might be present in x.y.1, x.y.2, x.y.3, and so on. This is to ensure that upgrades complete successfully. But HPE does not support using the component in later MEPs (x.y.1, x.y.2, x.y.3, and so on), and the last supported MEP version remains x.y.0.

**Discontinued for MEP 7.0.0 and later in September 2020. To be discontinued for MEP 5.0.x and MEP 6.3.x when those MEPs reach end of life.